Eruv Boundary Distance Calculator

How this calculator helps

This page is built for a narrow and practical job: take a distance that you measured or estimated, express it in familiar units, and compare it with a halachic limit stated in amot. The calculator accepts a distance from an eruv boundary, lets you choose the unit in which that distance is currently known, and then converts the same value into meters, feet, amot, and mil. After that conversion, it compares the distance with one of three limit types: the common Techum Shabbat limit of 2000 amot, the smaller city-boundary extension of 70⅔ amot, or a custom amot value that you enter yourself.

That sounds simple, but the details matter. A person might know a route length from a map in meters, hear a walking limit described in amot, and then discover that different cubit standards produce different real-world distances. If you skip the conversion step, it is easy to compare unlike quantities and get an answer that feels precise but is not actually answering the same question. This tool exists to keep the unit conversion visible, consistent, and easy to check.

It is also worth stating one important conceptual point clearly. In everyday conversation people sometimes mention an eruv and techum in the same breath, yet they are not the same thing. An eruv usually relates to carrying within a defined area. Techum Shabbat concerns travel distance from one’s place of residence. This calculator does not replace local practice, maps, or rabbinic guidance. It is a distance-comparison aid that helps you translate an amot-based limit into a physical distance and see how far inside or beyond that limit a measured point appears to be.

What each input means in plain language

Distance from Eruv Boundary is the raw distance you want to evaluate. You may know that distance from a municipal map, a GPS app, a measuring wheel, an aerial image, or a local boundary diagram. The tool does not assume how you obtained the number; it only asks you to be honest about the unit and to keep that unit consistent with the measurement source.

Distance unit tells the calculator how to interpret the number you entered. If your map already gives meters, choose meters. If you paced out a route in feet, choose feet. If you already have the figure in amot, choose amot so the calculator can translate it into meters and mil using the cubit standard you selected. If you choose mil, the page treats 1 mil as 2000 amot, which means the length of 1 mil changes along with the cubit standard.

Cubit Length Standard is the key assumption behind every conversion into or out of amot. The same count of amot can occupy a smaller or larger real-world distance depending on which amah length you follow. This page includes two common presets: 48 cm and 57.6 cm. It also allows a custom cubit length in centimeters when you want to model a different standard or reproduce a local practice exactly.

Calculation Type chooses the limit against which your entered distance will be compared. Select Techum Shabbat Limit to compare against 2000 amot. Select City Boundary Extension to compare against 70⅔ amot. Select Custom Distance in Amot when you want the same conversion engine but with your own amot count. That can be useful for teaching, planning, or checking a published figure from another source.

Custom Cubit Length and Custom Distance (amot) only matter when their matching options are selected. They are hidden until needed so the form stays readable. When you use them, remember what those entries represent: centimeters per amah for the cubit field, and total amot for the custom limit field.

How the calculation works

The calculator performs two related jobs. First, it converts your entered distance into a common internal unit, meters. Second, it converts the selected amot-based limit into meters using the same cubit assumption. Once both numbers are expressed in meters, the comparison is straightforward: if your entered distance is less than or equal to the limit distance, the point is shown as within the selected limit; otherwise it is beyond the limit. The page also reports how much room remains or how much the distance exceeds the limit, both in meters and in amot.

When the input is already in amot, the conversion is especially direct:

Here c is the cubit length in meters. The selected limit uses the same structure:

After both values are in meters, the remaining allowance is simply:

Because the page also supports several unit choices, it helps to remember the core conversions behind the form. Feet are converted with 1 foot = 0.3048 meters. Amot are converted with the cubit length you selected. Mil are converted as 2000 amot, again using the same cubit length. That is why the cubit selector affects more than one displayed field.

More abstractly, the page still follows the general calculator pattern shown below, and those original MathML formulas are preserved here for readers who like the broader mathematical view:

In this specific calculator, the conversion factors are the weights that matter most. Once you see that, the result becomes easier to audit: if the cubit length grows, the physical length represented by a fixed number of amot also grows.

A worked example

Suppose your measured point is 350 meters from the relevant boundary and you want to compare that distance with Techum Shabbat using a 48 cm cubit. The limit is 2000 amot, so the page converts that limit into meters by multiplying 2000 by 0.48. The result is 960 meters. Since 350 meters is less than 960 meters, the point is within the selected limit. The remaining margin is 610 meters.

Now look at the same 350-meter input under the 57.6 cm cubit setting. The limit becomes 1152 meters rather than 960 meters. The point is still within the limit, but the remaining distance is larger. This is exactly why the cubit assumption is not a cosmetic setting. It changes the physical meaning of a limit stated in amot.

A smaller example shows the city-boundary extension more intuitively. Using 70⅔ amot with a 48 cm cubit gives about 33.92 meters. Using 57.6 cm gives about 40.70 meters. When the distances involved are short, even a modest shift in cubit size can noticeably move the answer.

When you use the calculator for your own case, the most reliable habit is to change one thing at a time. Keep the same measured distance and switch only the cubit standard. Then keep the cubit standard fixed and switch only the limit type. That makes it obvious which assumption is driving the change in the result box.

How to interpret the result responsibly

The first line of the result area restates the distance you entered. The second line shows its equivalent in all supported units. The third line tells you whether the distance is within or beyond the selected limit and by how much. That structure is helpful because it lets you verify the conversion before you rely on the comparison. If the converted distance looks suspicious, you can catch the problem before treating the within-limit or beyond-limit statement as meaningful.

The two most common mistakes are simple. One is entering the right number with the wrong unit. The other is forgetting that a value entered in amot or mil depends on the selected cubit standard. If your result seems surprising, check those first. After that, review whether your measured point really corresponds to the location you intended to test. A clean formula cannot correct a mistaken measurement origin.

This calculator should be treated as an educational and planning tool, not as a standalone halachic ruling. Local maps, the status of a boundary, how residence is defined for a specific case, and community practice may all matter. The most useful way to use the page is to arrive at a transparent number that you can then discuss intelligently with the relevant authority if needed.

Finally, remember what a good result looks like: the unit should match the question you are asking, the magnitude should seem plausible, and a small change in a major assumption should move the answer in a direction you expect. When all three are true, the calculator is doing what it is supposed to do—turning a difficult-to-compare set of measurements into a clear, checkable summary.