Call and
Signal
Menu

Operating Skills · Guide

How Repeater Offsets Work on the 2-Meter Band

Vertical radio antenna mounted above a roofline, with a cable running down its mast.

A repeater offset separates two frequencies: the repeater’s output, which your radio listens to, and its input, which your radio transmits on. Repeater Builder describes the offset as the difference between the two frequencies a repeater uses. For a US operator reading a 2-meter FM repeater listing, the practical question is: Given the frequency I hear, where must my radio transmit?

A 600 kHz offset is common on the 2-meter band, according to ARRL, but it is not a setting to assume for every repeater. The output, the signed offset or explicit input, and any access tone are separate pieces of information. Understanding what each one controls makes a listing easier to read—and gives you a way to check what your radio actually stored.

Which Frequency Is the Repeater’s Input?

“Input” and “output” are named from the repeater’s point of view. Its input is the frequency on which it listens. Its output is the frequency on which it transmits. Your radio has the opposite roles on that same pair: it transmits toward the repeater’s input and receives the repeater’s output. Repeater Builder explains that a repeater uses two different frequencies and calls the difference between them the offset.

That reversal is the central mental model. A frequency labeled repeater output is not where your radio should transmit merely because “output” sounds like sending. It is what comes out of the repeater, so it is what you listen to. Likewise, repeater input means the frequency going into the repeater from your radio.

`text

Your radio transmits ──► repeater input

Your radio receives ◄── repeater output

`

Repeater Builder gives a concrete example in which a radio listens on a repeater output of 145.270 MHz. When the operator presses push-to-talk, the example radio switches its transmitter to 144.670 MHz; when the operator releases push-to-talk, it returns to listening on 145.270 MHz. The frequency visible while listening and the frequency used while transmitting therefore have different jobs. The example describes that radio’s behavior; it does not establish that every radio will select the correct input automatically.

Imagine pausing before pressing push-to-talk and asking two questions: “What frequency am I listening to?” and “What frequency will my radio use when I transmit?” In this example, the answers are 145.270 MHz and 144.670 MHz, respectively. Calling both of them simply “the repeater frequency” would hide the distinction that matters for programming. The repeater’s output gives you a useful starting point, but the input must still be identified.

This is why a listing’s output frequency is the starting point for the calculations below. Begin with what your radio should receive, then use the listing’s signed offset—or its explicitly stated input—to determine what your radio should transmit. Do not reverse the labels just because you are thinking from your own radio’s perspective. In the next two examples, every frequency has both a repeater role and a radio role; keeping those labels attached makes the sign much less mysterious.

How the Minus and Plus Signs Change Your Transmit Frequency

ARRL identifies 600 kHz as a common offset on the 2-meter band. To calculate with frequencies written in megahertz, first express that amount in the same unit: 600 kHz = 0.600 MHz. The offset’s amount tells you how far apart the two frequencies are. Its sign tells you which side of the output the input lies on.

Start at the repeater output—the frequency your radio receives. A minus offset means your radio’s transmit frequency, which is the repeater input, is lower than that output. A plus offset means your transmit frequency is higher. The sign is not a description of the direction in which a signal travels through the repeater. It is an instruction for finding the input from the output.

ARRL’s negative-offset example gives a repeater transmitting on 146.64 MHz and listening 600 kHz below that frequency, on 146.04 MHz. Writing the calculation with the decimal places aligned makes both roles explicit:

`text

Repeater output / your receive: 146.640 MHz

Minus the listed offset: 0.600 MHz

Repeater input / your transmit: 146.040 MHz

146.640 MHz − 0.600 MHz = 146.040 MHz

`

The three-decimal-place notation does not change ARRL’s pair; 146.640 MHz is the same frequency as 146.64 MHz, and 146.040 MHz is the same as 146.04 MHz. On this pair, your radio listens on 146.640 MHz. When you press push-to-talk, it must transmit on 146.040 MHz; when you release it, it must listen to the 146.640 MHz output again. That is a negative offset because the input is below the output, not because the output is a “minus frequency.”

ARRL also gives the opposite direction: a repeater listening 600 kHz above 147.360 MHz, on 147.960 MHz. Here the output is again the starting point, but the signed operation changes:

`text

Repeater output / your receive: 147.360 MHz

Plus the listed offset: 0.600 MHz

Repeater input / your transmit: 147.960 MHz

147.360 MHz + 0.600 MHz = 147.960 MHz

`

For this positive pair, your radio listens on 147.360 MHz and transmits on 147.960 MHz while push-to-talk is held. Releasing push-to-talk returns it to receiving the 147.360 MHz output. The repeater still has an input and an output; only the input’s position relative to the output has changed.

These examples give a reusable calculation:

Listed output ± listed offset = repeater input = your radio’s transmit frequency.

The word listed matters. If a listing says “+600 kHz,” add 0.600 MHz to its output. If it says “−600 kHz,” subtract 0.600 MHz. If it supplies an explicit input, you can compare that input with the result as a check. The arithmetic is reliable for the values you enter, but it cannot establish that an assumed sign or amount is correct for a particular local repeater. ARRL notes that common repeater offsets can vary and advises checking a repeater directory or RFinder rather than relying only on the common pattern.

A useful way to catch a sign error is to label both ends before calculating. Write “output / receive” beside the starting frequency, and “input / transmit” beside the result. Then ask whether the result landed above or below the starting frequency as the listing specifies. That check does not replace local information; it helps you apply that information consistently.

Why the Local Listing Matters More Than a Familiar Pattern

ARRL describes a band plan as a voluntary division of a band intended to avoid interference between incompatible modes. Its 2-meter ranges provide context for reading a pair, but a range labeled “repeater inputs” or “repeater outputs” does not, by itself, identify the exact input of every repeater whose output falls nearby.

The two worked pairs illustrate why the ranges can look familiar. ARRL’s band plan lists 146.61–146.97 MHz as repeater outputs and 146.01–146.37 MHz as repeater inputs. ARRL’s negative example places its 146.64 MHz output in the first range and its 146.04 MHz input in the second. That is consistent with a lower input and a minus sign. The comparison is an illustration of a pattern, not a way to assign an input to an unverified station.

ARRL also lists 147.00–147.39 MHz as repeater outputs and 147.60–147.99 MHz as repeater inputs. Its positive example places the 147.360 MHz output and 147.960 MHz input in those respective ranges. This time the input is higher, illustrating a plus sign. Seeing which range contains a frequency may help you notice that you have swapped input and output, but it cannot tell you whether an individual listing has an exception.

For an actual station, use its current local listing or local coordination information to identify the output and either the input or the signed offset and amount. ARRL suggests a repeater directory or RFinder as possible places to check repeater details. Treat the entry as information to verify, not as a reason to disregard a conflicting, more specific local detail. Repeater Builder cautions that offset practices can differ by area and that circumstances can produce a unique offset for a single repeater.

Suppose an output looks as though it belongs to a familiar minus-offset pattern, but the current information for that particular repeater specifies an input that does not match your assumed 600 kHz subtraction. The decision is not to force the familiar calculation into the radio. Check the local pair and resolve the discrepancy before programming it. Conversely, if a listing provides both the input and a signed offset, calculating from the output lets you spot a mismatch that calls for clarification. Those are checks on the information for that station, not claims that a band-plan pattern overrides it.

This distinction also prevents a broader mistake: “common US 2-meter offset” is not the same claim as “all 2-meter repeaters use this offset.” ARRL calls 600 kHz common, while both ARRL and Repeater Builder warn that actual offsets can vary. Use the familiar pattern to understand a listing, then use the verified local pair to set your radio.

Program the Pair and Keep Tone Access Separate

Once you have a verified pair, translate it into settings from your radio’s point of view. The repeater output becomes your radio’s receive frequency. The repeater input becomes its transmit frequency. If the radio asks for a shift direction and amount, use the listing’s plus or minus sign and offset amount to produce that input. If it instead permits separate receive and transmit frequencies, enter the verified pair in those roles. In either case, compare the resulting transmit frequency with the verified input rather than stopping when the displayed output looks right.

For example, the ARRL minus pair calls for receiving on 146.640 MHz and transmitting on 146.040 MHz; the plus pair calls for receiving on 147.360 MHz and transmitting on 147.960 MHz. Those numbers illustrate what a correctly set pair looks like, not what any particular menu will display or which controls you must press. Repeater Builder’s example shows one radio switching frequency on push-to-talk, but that behavior in an example is not a promise that another radio will choose the right local split without checking.

A saved memory deserves the same check. ARRL describes a memory that, when used, sends and receives on the proper frequencies and also sends its specified 100 Hz tone. The point to carry over is that a useful stored memory contains the correct pair and, when needed, the correct access setting. It is not evidence that every model automatically determines an exceptional local input, nor is 100 Hz a default tone for other repeaters. ARRL advises consulting the transceiver’s user manual for memory-channel instructions and notes that transceivers handle CTCSS in their own ways. Use that manual to find your model’s controls; after saving, inspect the memory’s actual receive and transmit frequencies.

CTCSS tone access is separate from offset. The offset determines where your radio transmits. If the repeater requires a specified input CTCSS tone, the transmit-tone setting determines whether your signal carries that tone. ARRL explains that a repeater requiring the proper tone will not respond to a transmission that lacks it. A correctly calculated input frequency does not substitute for a required tone, and entering a tone does not correct a wrong input frequency. Check each against the local information independently.

There may also be a receive tone-squelch setting on your own radio. ARRL describes its distinct job: when a repeater transmits a CTCSS tone, a radio with receive tone squelch can be set to pass received transmissions only when that tone is present. That filter affects what you hear from the repeater. It is not the tone your radio sends to gain access. Because the transmit-access setting and receive filter have different jobs, do not assume their values must match. Check any stated input tone and output tone separately in the listing, and use the manual to identify which radio setting controls each function.

The compact programming model is therefore receive frequency, transmit frequency, transmit access tone if required, and optional receive tone squelch if applicable. Keep the first two tied to the verified pair and the tone settings tied to their separate purposes. That model works whether your radio presents an offset menu or separate transmit and receive entries; the model-specific procedure belongs in its user manual.

If the Repeater Doesn’t Respond

A missed response is a reason to inspect the settings, not proof that the offset alone is wrong. Start with the current local information for the repeater rather than a remembered band-plan pattern. ARRL recommends checking repeater listings because common offsets can vary, and Repeater Builder warns of local and individual exceptions.

First, confirm that the frequency you are monitoring is the repeater output. That is the frequency your radio should receive, not necessarily the one it should use during push-to-talk. Next, inspect the radio’s actual transmit frequency, including what its stored memory will use. Compare that number with the listed input. If they disagree, check the shift sign and amount, or the separately entered transmit frequency, against the local pair. Working backward from the displayed transmit frequency can reveal a reversed sign or an assumed 600 kHz amount where the local details specify something else.

Then check access separately. Does the listing specify a required transmit CTCSS tone, and is your radio set to send that value? ARRL states that a repeater requiring a proper tone will not respond without it. Do not change an otherwise verified frequency pair merely to compensate for a missing or incorrect tone; these are independent checks.

There is a different receive-side question if you expect to hear a repeater transmission but your radio remains silent while receive tone squelch is enabled. Compare that optional filter with any listed repeater output tone, or disable the filter as appropriate for your radio and the listing. ARRL explains that receive tone squelch admits a transmission only when the configured tone is received. Adjusting this filter is not the same as changing the transmit tone used for access.

The resulting check is narrow: Are you receiving the verified output, transmitting on the verified input, accounting for any local split, and using the applicable tone settings for their proper jobs? Matching those details resolves the offset-and-tone questions addressed here. It does not, by itself, promise a response or a contact.