Channel
@alverisunion
On this record: Previous handles · Growth · Engagement · Posts · Citations · Cite this entry
4subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003769214014 |
|---|---|
| Type | Channel |
| Username | @alverisunion |
| Created | Between 1 February 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 30 August 2026 |
| On Telegram | t.me/alverisunion |
@alverisunion was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 15:53 | 4 | +1 |
| 13 Aug 2026, 14:31 | 3 | no change |
| 7 Aug 2026, 03:12 | 3 | first reading |
2 posts held, back to 29 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 page of 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 2 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
unions Nurel 1. @haitaniofficial - @by8hl 2. @chasewwwws - @A1S85 3. @Maarvelln - @Qnsw1 4. @teyitknf - @hidzll 5. @tw1nskii - @LuvMyEmil 6. @AG1REST - @lulxdy 7. @anavr11nn - @bszhae 8. @Beverlyfm - @evsxk 9. @wilsonfml - @mdlllx 10. @belfegorfml - @Mnhwzldd 11. @sulukchor - @S07les 12. @nrn05q - @drakularr 13. 14. @llnect - @tukumka 15. @ALKZR1 - @Tenz01 16. @darenovy - @orol1un 17. @nekomakg - @orollun 18. @motion…
Union Rules 1. +50 2. 1:1 3. папка: рп, вз, актив по возможности 4. рекламные посты размещаются на 3-4 часа 5. выходные сб и вс 6. с рейд деятельностью не сотрудничаем 7. чистки не проводим и в них не участвуем 8. при конфликте будем на нейтральной стороне 9. администрация оставляет за собой право отказать в сотрудничестве без причин 10. Рп ваших постов не будет, если ваш кф/семья/шоп/исд или след в ресте разрывы есл…
Showing the 2 most recent of 2 posts we hold for @alverisunion. 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“unions Alveris” (@alverisunion), 4 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/alverisunion.
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.