ChatterBack🔍Join
States/Kentucky/MeshCore/SCKY | TZV TEMP-6ABE
MC

SCKY | TZV TEMP-6ABERoom server

6abe9672638b · Kentucky
● Heard 5 h agovia analyzer.nashme.sh
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.34 / 1.00
C is 0.30 and above. 0.45 would make it B.
6007
relayed · 24 h
  • Bridgeweight 0.300.00 × 0.30 = 0.000

    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.57 × 0.25 = 0.143

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

  • Redundancyweight 0.250.00 × 0.25 = 0.000

    What breaks if it vanishes. High means nothing else covers its job. Something else already covers what it does, so losing it would not split the mesh.

  • Trafficweight 0.201.00 × 0.20 = 0.200

    How much it actually relayed, measured rather than inferred from the map.

What would actually change this

  • This is a room server, not a repeater

    These four axes measure relaying, and passing other people’s traffic is not what a room server is for. A low grade here is close to meaningless as a judgement of it — it is being marked on somebody else’s exam.

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

47 samples · last 30 days
Neighbours33–5

Node

from the mesh, refreshed every few hours
Protocol
MeshCore
Node ID
6abe9672638b
Role
Room server
Hardware
-
Preset
-
Channel
-
Firmware
-
Neighbors
3
Relayed 24 h
6007
Adverts seen
270
Coverage
0.57
Usefulness
C · 0.34
First seen
2026-09-08