Channel
@amtenebris
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
10subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001246334236 |
|---|---|
| Type | Channel |
| Username | @amtenebris |
| Created | Between 1 March 2018 and 12 April 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/amtenebris |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 10:04 | 10 | no change |
| 7 Aug 2026, 20:11 | 10 | first reading |
19 posts held, back to 12 April 2020 — 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 19 posts for this entry, the most recent from 30 June 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
➥ EXCLUSIVE @AppleMusicsTM
The account of the user that owns this channel has been inactive for the last 1 month. If it remains inactive in the next 10 days, that account will self-destruct and this channel will no longer have an owner.
https://youtube.com/channel/UCoMRYUHFeGEDg1HznfN_RTw
https://youtu.be/V0ywiuq_rAw
https://youtu.be/SpIwY15FWrs
https://youtu.be/_22WYr4IWQo
https://youtu.be/rR2FMQiDIA4
https://youtu.be/Q3mJ3lbS0n0
How to Secure Your Instagram Accounts From Hackers 2020 Tips & Tricks Hacks & Strategies # Push to the limit Dont Forget To subscribe please https://youtu.be/5YCwrvAHnA8
https://youtu.be/n5JjpJLRW80
https://youtu.be/1wqiNPRXT_g
Showing the 12 most recent of 19 posts we hold for @amtenebris. 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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“AMTENEBRIS” (@amtenebris), 10 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/amtenebris.
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.