Telegram RegisterThe public register of Telegram

Channel

ISP Mir@net

@ispmiranet

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

182subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001686144050
TypeChannel
Username@ispmiranet
DescriptionОфіційний канал інтернет провайдера Mir@net
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live15 August 2026
Measurements held2
On Telegramt.me/ispmiranet

Growth

1827 Aug 2026, 21:28 — 182 subscribers8 Aug 2026, 12:46 — 182 subscribers7 Aug 2026, 21:288 Aug 2026, 12:46
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 181–183 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:46182no change
7 Aug 2026, 21:28182first reading

Engagement

18 posts held, back to 9 October 2024the 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 18 posts for this entry, the most recent from 1 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
6
Links
13

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

50 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 30.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1530.0%
🙏1020.0%
👍918.0%
😢918.0%
👌36.00%
🤝36.00%
💘12.00%

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 8 of the 18 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 50reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 9 October 2024 to 1 June 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.

Recent posts

1 Jun 2026, 10:24 UTC244 viewsread 8 August 2026

Увага! 02.06.2026р. з 10:00 до 16:00 будуть проводитись аварійні роботи (ремонти після ворожих обстрілів). Доступ до мережі Інтернет в с.Підліснівка та в с.Степне буде в цей час тимчасово недоступним до закінчення виконання аварійних робіт. Дякуємо всім за розуміння! https://www.facebook.com/share/p/18jnjreBvV/

23 May 2026, 08:18 UTC397 viewsread 8 August 2026

⚠️ Шановні сумчани! Завтра у місті Суми буде повністю відсутнє електропостачання у зв’язку з проведенням робіт на мережах. Час відключення: з 06:00 до 16:00

28 Apr 2026, 06:40 UTC404 viewsread 8 August 2026
Forwarded from @sumyregionPhoto

Влучання російського безпілотника у Сумах вночі, – Суспільне Дрон впав поблизу дитячого майданчика та зупинки у Ковпаківському районі. Він пошкодив п'ять приватних будинків та магазин. У будівлях вибито вікна. Підписатись | Відправити новину

28 Apr 2026, 04:36 UTC353 viewsread 8 August 2026

28 квітня 2026р об 00:04 внаслідок військової агресіі було пошкоджено лінії звʼязку р-ну Добровільна. Тривають аварійно-відновлювальні роботи. Дякуємо всіх за розуміння! https://www.facebook.com/share/p/1JPt929Yju/?mibextid=wwXIfr

17 Apr 2026, 10:06 UTC419 views2 reactionsread 8 August 2026

Роботи по модернізації лінії - закінчено

2

17 Apr 2026, 08:53 UTC415 viewsread 8 August 2026

17 квітня в м.Суми по вулицях Добровільна, Конотопська Ударників з 11 до 14 будуть проводитись роботи по модернізації ліній зв'язку. Зв'язок тимчасово зникне до завершення робіт

17 Jan 2026, 19:04 UTC682 views13 reactionsread 8 August 2026

17.01.2026 Внаслідок ворожої атаки зафіксовано пошкодження ліній звʼязку (за містом). Без публікації назви населених пунктів, ми знаємо про пошкодження і де вони! Чекайте на завершення аварійних робіт! Дякуємо всім за розуміння і терпіння!

🙏10🤝3

26 Nov 2025, 10:07 UTC≈1,460 viewsread 8 August 2026

https://www.facebook.com/share/p/1Jucjx9QNZ/?mibextid=wwXIfr

18 Nov 2025, 13:44 UTC623 views0 reactionsread 8 August 2026

Масовий збій фіксують у роботі низки українських сайтів деяких соцмереж та сервісів. Попередньо, є проблеми із Cloudflare — провайдером мережевої безпеки, прискорення роботи сайтів та доставки контенту (CDN).

11 Nov 2025, 10:47 UTC494 views2 reactionsread 8 August 2026

Шановні користувачі в м.Суми! Зв'язок зникне на 15 хв. планові роботи на обладнання

👍2

Showing the 12 most recent of 18 posts we hold for @ispmiranet. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“ISP Mir@net” (@ispmiranet), 182 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ispmiranet.

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.