Fanegada area converter
One fanegada of Castile is about 6439.5 m², or 0.644 hectares and 1.5912 acres. Pick your region's variant, because the fanegada is not the same size everywhere, and get all three units at once. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Fanegada
- 1
- Decimal places
- 4
- Variant
- es_castilla_6439_5
- M2
- 6,439.5
- Ha
- 0.644
- Acre
- 1.5912
Convert Spanish/Latin American fanegada agrarian area by regional variant. Search intent: fanegada to hectares. No network calls, no random seeds, and no server state are required for a correct answer. Failed jobs are not billed. Landings target the
An old land measure that changes by region
The fanegada is a traditional unit of farmland area used in Spain and Latin America. It has no single size: regions kept their own values, and that difference matters when you compare an old land description with a modern measurement. This converter lets you choose the regional variant before calculating. In the Castile variant, one fanegada is about 6439.5 square meters. From there, the result comes out in square meters, hectares and acres at the same time, the three units most often used to compare a surface today.
How the conversion works, and mistakes to avoid
The calculation is a multiplication: the number of fanegadas times the square meters of the chosen variant. Hectares come from dividing those square meters by ten thousand, and acres from applying the matching conversion factor. The most common mistake is using the Castile value for a plot in another region, which changes the whole surface. Another is rounding at every step; the converter rounds once, at the end, to the decimals you ask for. Finally, do not mix up hectares and acres: one fanegada of Castile is 0.644 hectares but 1.5912 acres.
How it works
Convert Spanish/Latin American fanegada agrarian area by regional variant. Castile ≈6439.5 m²; other regional constants available as enum variants. No network calls, no random seeds, and no server state are required for a correct answer.
Failed jobs are not billed. Landings target the stated search intent with precise keywords. Prefer explicit units and ranges over silent coercion of bad types.
When a field is optional, defaults are documented in params and echoed in the output.
When to use it
Use when the search intent matches this tool. Convert Spanish/Latin American fanegada agrarian area by regional variant. No network calls, no random seeds, and no server state are required for a correct answer.
Failed jobs are not billed. Landings target the stated search intent with precise keywords. Prefer explicit units and ranges over silent coercion of bad types.
When a field is optional, defaults are documented in params and echoed in the output.
FAQ
Locales?
EN-only delivery; Nitro hydrates the other seven languages.
How many square meters are in a fanegada?
It depends on the region. In the Castile variant, one fanegada is about 6439.5 m², while other regions use their own values. That is why the converter asks for the variant before it calculates.
How many hectares and acres is a fanegada of Castile?
With four decimals, one fanegada of Castile gives 0.644 hectares and 1.5912 acres. The converter shows both figures next to the square meters, so you do not need to chain conversions.
Why do I have to choose a regional variant?
Because the fanegada is a traditional farmland measure and regions across Spain and Latin America kept different sizes for it. Using the Castile value for land from another area gives the wrong surface.
How is the result rounded?
You choose how many decimals you want. Rounding happens only once, at the end, from the unrounded result and with halves rounded up, so no error builds up from intermediate steps.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/fanegada-area \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"m2":6439.5}'const res = await fetch("https://api.kit.forhosting.com/conv/fanegada-area", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"m2": 6439.5
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/fanegada-area",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"m2": 6439.5
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/fanegada-area", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"m2":6439.5}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"m2":6439.5}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/fanegada-area", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"m2": 6439.5
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.fanegada_area",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
How it works
The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
Inputs, limits and rounding
Outputs echo inputs for logging. No network calls, no random seeds, and no server state are required for a correct answer. Failed jobs are not billed. Landings target the stated search intent with precise keywords. Prefer explicit units and ranges over silent coercion of bad types. When a field is optional, defaults are documented in params and echoed in the output. Provide required JSON fields. Optional decimals use half-up once from raw IEEE values. Invalid types or ranges raise invalid_input. The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
When to use it
The calculator is free in the browser, deterministic, and identical in the API path. Inputs are validated before any arithmetic so invalid payloads fail with invalid_input. Half-up rounding is applied once from raw IEEE results when decimals are requested. Use the same JSON contract from spreadsheets, CMS hooks, automation, or teaching demos.
Integration use cases
Quick check
Use the free widget to verify a formula before production.
Automation
Call the API with the same JSON contract from scripts or CMS.
Teaching
Show pinned golden examples without proprietary software.
Technical questions
Is the browser widget free?
Yes. Tier A is free client-side with the same core as the API.
Does it use the network?
No. Computation is local and deterministic.
What on bad input?
invalid_input is thrown; failed jobs are not billed.
API compatible?
Yes — same JSON fields as params.json.