4 Jun 2026, 20:35 UTC100 viewsread 9 August 2026
The Toulon Peak repeater is back to normal service. Also confirmed Winnemucca is still connected. Happy hamming!!!
Channel
SNARS Repeater Status Broadcast
@snars_repeaters
On this record: Growth · Engagement · Posts · Cite this entry
110subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001296627683 |
|---|---|
| Type | Channel |
| Username | @snars_repeaters |
| Created | Between 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/snars_repeaters |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 09:18 | 110 | -1 |
| 9 Aug 2026, 06:47 | 111 | no change |
| 8 Aug 2026, 20:53 | 111 | +1 |
| 7 Aug 2026, 23:35 | 110 | first reading |
Engagement
20 posts held, back to 7 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
4 Jun 2026, 20:12 UTC100 viewsread 9 August 2026
We have received authorization from Dave Metts to turn the Toulon Peak 146.925 repeater back on. L3/Harris ultimately determined that there was no noise or interference coming from the SNARS equipment, it sounds like it was misinterpretation of what they were seeing on the their analyzer.
2 Jun 2026, 23:23 UTC109 viewsread 9 August 2026
The 146.925 repeater on Toulon Peak is currently down due to a reported interference issue with NDOT public safety equipment at the site. Efforts are being made to mitigate the issue as quickly as possible.
16 May 2026, 19:51 UTC167 viewsread 9 August 2026
ATTN: The 444.875 Lobdelle repeater will be offline temporarily while site maintenance is being performed.
3 Dec 2025, 15:42 UTC334 viewsread 9 August 2026
For those DMR users, the Eagle Ridge repeater is down due to a network interface issue with the radio. This radio is a Motorola SLR5700, we’ll get it back on the air as soon as possible.
1 Dec 2025, 21:10 UTC358 viewsread 9 August 2026
SNARS Linked Repeater System - UPDATES & Noon Net frequencies Virginia Peak Repeater 147.030 + pl123.0 Because of a severe desense issue, the 147.030 repeater is currently in a cross-band configuration and does not function as a normal repeater. It is still connected to the other repeaters in the SNARS Linked Repeater System so you can communicate with other users heard coming through 147.030. NOTE: If you use th…
1 Dec 2025, 14:50 UTC177 viewsread 9 August 2026
Peavine has been reconnected to the rest of the system. With the exception of Virginia Peak being in cross band, everything is back to normal.
1 Dec 2025, 13:40 UTC170 viewsread 9 August 2026
The 147.210 Peavine repeater is turned back on this morning, the interference seems to be gone. It is currently in stand alone configuration to see if the interference is going to return.
27 Nov 2025, 17:40 UTC192 viewsread 9 August 2026
Whatever the issue was with Peavine seems to have resolved itself. It is back to normal this morning!
5 Nov 2025, 19:38 UTC244 viewsread 9 August 2026
One of numerous power outages appears to have the 147.210 Peavine repeater down. No estimated time of restoration by NV Energy.
15 Oct 2025, 13:34 UTC291 viewsread 9 August 2026
Whatever was causing the 146.610 Ophir repeater to be stuck in transmit, appears to have resolved itself. It functioned properly during last night’s DMR net.
14 Oct 2025, 17:32 UTC263 viewsread 9 August 2026
The 146.610 repeater, on Ophir Peak, appears to be stuck in Transmit. This will be investigated at earliest opportunity. At this time, it is unusable.
Showing the 12 most recent of 20 posts we hold for @snars_repeaters. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 24 August 2026 — this entry's latest reading, not the date you are reading this.
“SNARS Repeater Status Broadcast” (@snars_repeaters), 110 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/snars_repeaters.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.