Channel name was changed to «げ TEN3BR4E い🔒🔒🔒»

Channel
げ TEN3BR4E い🔒🔒🔒
@ten3braejpn
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
343subscribers
-3 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 | -1002670157516 |
|---|---|
| Type | Channel |
| Username | @ten3braejpn |
| Created | Between 1 March 2025 and 18 May 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/ten3braejpn |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 21:06 | 343 | -2 |
| 8 Aug 2026, 12:37 | 345 | -1 |
| 8 Aug 2026, 06:50 | 346 | no change |
| 7 Aug 2026, 16:01 | 346 | first reading |
Engagement
4 posts held, back to 18 May 2025 — 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 4 posts for this entry, the most recent from 20 December 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
65 reactions across 2 posts, in 7 distinct kinds. The most used accounts for 27.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5325881737643847450 | 18 | 27.7% | |
| custom 5325606739477817150 | 14 | 21.5% | |
| custom 5325853974975244331 | 14 | 21.5% | |
| custom 5323257405251806081 | 8 | 12.3% | |
| custom 5325767066312009203 | 5 | 7.69% | |
| custom 5323397962351535610 | 3 | 4.62% | |
| custom 5325814212168019691 | 3 | 4.62% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 3 of the 4 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 65reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 18 May 2025 to 20 December 2025, 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
кф закрывается, и, возможно, мы больше не вернёмся. а если всё же судьба приведёт нас обратно то, это будет уже совсем новая история. патент за нами. Всем удачи, тенебрята муа
Signed coffee moon
(🌟) Subscribe to the channel Read the rules Include an initial in your nickname Submit a request in the chat ✅
custom 532588173764384745018custom 532560673947781715014custom 532585397497524433114custom 53232574052518060816custom 53233979623515356103custom 53257670663120092033custom 53258142121680196913
Sticker, posted without a caption
custom 53232574052518060812custom 53257670663120092032
Signed L̴͛E̹͘O̼͑͂N͎̓̕
Showing the 4 most recent of 4 posts we hold for @ten3braejpn. 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.
Citation-graph rank
Citation-graph rank — 1,200,228 of 1,480,975entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@ten3braejpn named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 9 August 2026 – 9 August 2026
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“げ TEN3BR4E い🔒🔒🔒” (@ten3braejpn), 343 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ten3braejpn.
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.