Coyote Mobile2offline 50d
!37fe142eCLIENTHELTEC_MESH_NODE_T114
Identity
self-reported- Long name
- Coyote Mobile2
- Short name
- COY2
- Node ID
- !37fe142e (939398190)
- Role
- CLIENT
- Hardware
- HELTEC_MESH_NODE_T114
- Firmware
- -
- Licensed
- no
- First heard
- Aug 31, 2026, 14:34:35
- Last heard
- Sep 03, 2026, 20:00:31
- Public key
- ec43216f2eb5463f3632e5a9b2e457eafe741edfe04ccd3426cb16a218cff461
First heard
Aug 31, 2026, 14:34:35
Last heard
50d ago
Packets / receptions
24 / 24
Position
unknown
Nearby (direct links)
Loading nearby nodes…
What it transmits (14d)
No packets in the window.
On network 54 days~0 packets/day
Activity (day x hour, America/Chicago)
Sun
Mon
Tue
Wed
Thu
Fri
Sat
0h6h12h18h23h
Recent messages
- 51d[LongFast]5x5. Reading both messages.
- 51d[LongFast]👋
- 52d[LongFast]No caffeine for 8 month. I’d like to say it gets easier. It does not. 🤠
- 53d[LongFast]Yep. 5x5
- 53d[LongFast]Testing msh/US/IN/bloomington. Ping.
- 53d[LongFast]Considering a meshtastic/meshcore dual repeater out here. We’ve got fair elevation. Just planning at the moment.
- 53d[LongFast]173 miles or so. Looks like my MQTT routing is up and running. Not RF from Bloomington 🤠
- 53d[LongFast]New node. Test ping.
Reliability & reach
Heard direct
-
Gateways
0
Brokers
0
Farthest direct
-
Uptime
-
Chattiness
72%ile
Advertisements (7d)
0
ChannelsLongFast
RF neighbor graph
green = this node hears them; amber = they hear this node.
Uptime & availability
Avail 24h
0%
Avail 7d
0%
Avail 30d
0%
Uptime
-
Reboots 30d
0
Longest run
-
Heard, hourly (7d)no reboot in 30d
heard no dataoldest left, newest right
Biography
- Aug 31, 2026, 14:34:35public_keyec43216f2eb5463f3632e5a9b2e457eafe741edfe04ccd3426cb16a218cff461
- Aug 31, 2026, 14:34:35roleCLIENT
- Aug 31, 2026, 14:34:35hw_modelHELTEC_MESH_NODE_T114
- Aug 31, 2026, 14:34:35short_nameCOY2
- Aug 31, 2026, 14:34:35long_nameCoyote Mobile2
Heard by gateways
| Gateway | Status | Last direct | Last relayed |
|---|---|---|---|
| Not yet heard by any gateway. | |||
Best gateways (advisor)
Ranked by reception quality and consistency. Use this to spot redundant coverage and gaps.
| Gateway | Status | Direct | Relayed | Avg RSSI | Avg SNR |
|---|---|---|---|---|---|
| No gateway has heard this node yet. | |||||
Traffic fingerprint
Profile: insufficient data0 receptions, UTC hours
| 0 | 6 | 12 | 18 | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sun | ||||||||||||||||||||||||
| Mon | ||||||||||||||||||||||||
| Tue | ||||||||||||||||||||||||
| Wed | ||||||||||||||||||||||||
| Thu | ||||||||||||||||||||||||
| Fri | ||||||||||||||||||||||||
| Sat |