ChatterBack🔍Join
States/Oklahoma/MeshCore/Jackalope
MC

JackalopeRepeater

db9bef260366 · Oklahoma
● Heard 4 h agovia corescope.tulsa-mesh.com
Position as last reported by the node. Members’ own nodes can be shown at grid precision instead.

How this repeater scores

CoreScope · relative to this mesh
C
0.31 / 1.00
C is 0.30 and above. 0.45 would make it B.
5
relayed · 24 h
  • Bridgeweight 0.300.16 × 0.30 = 0.048

    How much of the mesh has to pass through it. A chokepoint between two halves of a network scores high. Traffic has other ways round. Not a fault - it means the area is well connected.

  • Coverageweight 0.250.42 × 0.25 = 0.104

    How much of the mesh it can reach, weighted so near neighbours count more than distant ones.

  • Redundancyweight 0.250.61 × 0.25 = 0.153

    What breaks if it vanishes. High means nothing else covers its job.

  • Trafficweight 0.200.01 × 0.20 = 0.002

    How much it actually relayed, measured rather than inferred from the map. It is carrying little traffic compared with the busiest repeater here.

What would actually change this

  • About typical for the area

    Coverage of 0.42 against an average of 0.45 across 54 repeaters within 25 miles.

  • A low Bridge is not a fault

    Bridge measures how much traffic has no choice but to pass through this node. It falls when neighbours put up repeaters that cover the same ground — so it can drop without anything changing here at all. There is nothing to tune.

  • Reachable, but not on anyone's path

    It can hear plenty and is relaying little, which usually means traffic has shorter routes. That follows from where the people are, and tends to change on its own as the mesh grows.

Every axis is scored against the other repeaters this analyzer can see, so 1.00 means “the best of these” rather than perfect, and a grade here is not comparable with one from another mesh. CoreScope’s own note on the bands is that they are a first cut, not tuned against real data — so treat the letter as a rough impression and the number as the real answer.

History

4 samples · last 30 days
Neighbours108–10

Node

from the mesh, refreshed every few hours
Protocol
MeshCore
Node ID
db9bef260366
Role
Repeater
Hardware
-
Preset
-
Channel
-
Firmware
-
Neighbors
10
Relayed 24 h
5
Adverts seen
8
Coverage
0.42
Usefulness
C · 0.31
First seen
2026-10-12