Channel
@flespi_noc
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
193subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001144338466 |
|---|---|
| Type | Channel |
| Username | @flespi_noc |
| Created | Between 1 January 2017 and 30 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/flespi_noc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 00:43 | 193 | +1 |
| 8 Aug 2026, 11:50 | 192 | no change |
| 7 Aug 2026, 21:09 | 192 | first reading |
20 posts held, back to 10 July 2026 — 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 11 July 2026. An engagement rate over an empty window would be a number about nothing.
89 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 83.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 74 | 83.1% | |
| 👎 | 15 | 16.9% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 89reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 10 July 2026 to 11 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
We have restored all intervals data in analytics. All systems are stable. If you experience any issues, please report them in the flespi chat — we will take care of it. A more detailed incident report will be published later in July. Sorry for any inconvenience and for the ruined Friday - we did our best to make it as short as possible.
👍17
All systems are stable and the load is fully under control. We are still restoring analytics intervals — currently at ~50% progress, with an estimated 2 more hours until fully restored. If you experience any issues, please contact us in the flespi chat. It's 1 AM on Saturday our local time, and almost the entire engineering team is still in the office (since 8 AM Friday), running the restoration process and keeping…
👍13
We diagnosed that analytics system has intervals data gaps due to the downtime. We are working to restore the data.
👍8
Mostly the load is now passed and full window for telematic data ingestion is opened already for dozens of minutes. Still we have a huge load and still periodically some remote nodes report delays. So we may expect some more short downtime reports. We are now checking other systems down the data flow such as analytics and streams, checking the databases and services consistency and all these minor things that should…
#eu: downtime ended, period: 95 second(s)
#eu: downtime started, error: Simulated telematics device timed out waiting for recently added command. Usually this indicates the problem with flespi Telematics Gateway.
#eu: downtime ended, period: 48 second(s)
#eu: downtime started, error: Simulated telematics device timed out waiting for recently added command. Usually this indicates the problem with flespi Telematics Gateway.
#eu: downtime ended, period: 101 second(s)
#eu: downtime started, error: Simulated telematics device timed out waiting for recently added command. Usually this indicates the problem with flespi Telematics Gateway.
👎2
#eu: downtime ended, period: 262 second(s)
#eu: downtime started, error: Simulated telematics device connected to the channel, sent the packet with message, but channel didn't replied to it. Usually this indicates the problem with flespi Telematics Gateway.
Showing the 12 most recent of 20 posts we hold for @flespi_noc. 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.
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.
“flespi noc (eu)” (@flespi_noc), 193 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/flespi_noc.
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.