Channel
@tehbunker
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
63subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001598878631 |
|---|---|
| Type | Channel |
| Username | @tehbunker |
| Created | Between 1 September 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/tehbunker |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 19:12 | 63 | -1 |
| 10 Aug 2026, 03:15 | 64 | no change |
| 7 Aug 2026, 06:29 | 64 | first reading |
17 posts held, back to 10 July 2024 — 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 17 posts for this entry, the most recent from 14 September 2024. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Use my referral link to claim back your lost sold. I reclaimed 6 sol from one wallet. Bot (telegram): https://t.me/solclaimiobot?start=1571223812 Website (phantom); https://app.solclaim.io/?ref=1571223812
Signed Justin
Mooner coming.
Signed Justin
4HEdSVfSyBvDQLALpQj1iWruakRDBBvdLUpGyV2hjyxD
Signed Justin
$SMH 25k experienced CTO lead.
Signed Justin
Degen Bunker pinned Deleted message
Aped this cto! 15k! HaGRXemtXtJYSnFPo3dqMopxNEivSmxyHqjpq9dsyKiz https://t.me/KENFIRSTDOGE
Signed Justin
Threw dust in this cto 0xda5a2f10536358f71be37d5c0e384882c6d0ada6
Signed Justin
Fade me more pussies
Signed Justin
From Eca to 150k
Signed Justin
ECA: 0xB1DB1721E194e72d692b20cAF3214cC00CDC92e5
Signed Justin
Eth play coming 1-2 hours!
Signed Justin
Sticker, posted without a caption
Signed Justin $WITH
Showing the 12 most recent of 17 posts we hold for @tehbunker. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Degen Bunker” (@tehbunker), 63 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/tehbunker.
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.