Repeaters / repeater
◎

BUR-MNK-Temp

Repeater3.4 mi NW of Woburn Center

Community infrastructure that passes messages along the mesh; it does not write them. Numbers are a sample from the relay paths our Woburn radio heard. What is a repeater?

Messages relayed, 7 days1,843
Hops from our radio1
Last heardOct 14, 2:28 PM
First heardOct 6, 2:28 PM

On the map

Position sent by the repeater

Its advertised position: 42.52213, -71.18588 · open in OpenStreetMap.

Orange pin: this repeater · blue lines and dots: repeaters it links with on relay paths our radio heard · green dots: other repeaters within 10 mi.

Health

Not heard recently
Heard by us for 11 days; 14 adverts received. Last heard Oct 14, 2:28 PM.

Linked and nearby repeaters

  1. TEMP-MNK-1 1.5 mi S · linked on 62 relay paths
  2. BUR-Fox Hill 2 0.6 mi W · linked on 25 relay paths
  3. BUR-NorthEast-4 0.1 mi NW · linked on 23 relay paths
  4. BUR-NorthEast-2 0.4 mi E · linked on 10 relay paths
  5. BUR-SouthWest-2 3.6 mi SW · linked on 6 relay paths
  6. BUR-NorthEast-1 0.1 mi W · linked on 3 relay paths
  7. BUR-MNK-Temp-2 0.0 mi W
  8. MNK-room 0.1 mi N
  9. BUR-MNK-Temp-3 0.1 mi NW
  10. BUR-NorthEast-3 0.4 mi N
  11. BUR - Fox Hill 0.7 mi W
  12. TEMP-MNK-2 1.0 mi W

Activity, last 30 days

Packets our Woburn radio heard through it each day, oldest on the left. 22 quiet days (nothing heard through it).

Region tags it carries

  • unscoped (travels everywhere) 100%
Everything it relayed was unscoped. If you run it, adding the bos region keeps local traffic local (see the Community page).

Busiest hours

Most traffic around 2 pm and 6 pm (Eastern).

Channels through it

#test 6Public 3#cdmesh 1#ct 1#ma-mesh 1#nhmesh 1

Neighbouring repeaters

Repeaters just before or after it on message paths: who it hears and who hears it.

Who relies on it

  1. Roberto🤖 12 messages
  2. Fairfield 🤖 4 messages
  3. 🤖LathamWatch🤖 3 messages
  4. P-T1000E 2 messages
  5. Igor's Grumpy Bot 2 messages
  6. Rakpoc 2 messages
  7. WO2H-V4-2 🚒 1 messages
  8. SMOKE_JUMPER 1 messages
Senders whose public messages crossed it most often, last 30 days.

Device

Device: Unknown
Is this your radio? Tell us under Settings → My radio. See the radios people use.

Links

2 mi4 miBUR-MNK-Temp and TEMP-MNK-1: 18 packets a day, 1.5 miBUR-MNK-Temp and BUR-NorthEast-4: 6 packets a day, 0.1 miBUR-MNK-Temp and BUR-Fox Hill 2: 6 packets a day, 0.6 miBUR-MNK-Temp and BUR-NorthEast-2: 3 packets a day, 0.4 miBUR-MNK-Temp and BUR-SouthWest-2: 1 packets a day, 3.6 miBUR-MNK-Temp and our rooftop: 1 packets a day, 3.4 miTEMP-MNK-1BUR-NorthEast-4BUR-Fox Hill 2BUR-NorthEast-2BUR-SouthWest-2our rooftopBUR-MNK-Temp
Repeaters next to it on message paths (thicker = busier). Dashed grey: unscoped traffic only. Full view

Messages it carried

Oct 13, 8:24 PM
Public · 9 hops · WO2H-V4-2 🚒Got ya in troy NY
Oct 13, 7:44 PM
#ct · 13 hops · SMOKE_JUMPERToday was a disaster.
Oct 13, 6:10 PM
#ma-mesh · 6 hops · JTEN@[WSNS] hello from Andover
Oct 13, 4:58 PM
#test · 15 hops · Fairfield 🤖@[jim (ARS-ELG)] 5 hops, 2-byte recv 16:58:24 EDT Your clock is ok
Oct 13, 4:35 PM
#testing · 9 hops · txtMesh💬@[Ewel] Your ping was heard by 8 of 14 cdme.sh observers across ~46 miles, 4 hops deep, on 16 repeaters total. [1/3]
Public messages whose path crossed this repeater on the way to our radio. A repeater does not write messages; it passes them on.