🤩𝘵h𝖊υᩛׄ 𐐼𝓻e lоoӄִׄιn𝚐 𝓪t . .🔤NʝЕ̠𝐂T ݁ 🎀 — ➿🔡➿🔡➿ ➿ — ₊ ⊹ ݁ ₊ ⊹ 🥹A🔤dit🎀 : on 👁 🎀 ⠀🥹n𐐫 𝐬ꪱׁׁׁׅׅׅgη𝓪l 🌟݁ ₊ ⊹ #𝔒T2 🌟 🥹 🤩𝕡eɕׄ𝖎a𝘭 𝐅ꫀׁׅܻ݊αtυr𝘦𝖘 : 🥹 υnаνa𝐢𝚕aϐ𝓵ꫀׁׅܻ݊ # отӄִׄթыв̠𝓪𝚎м н𐐼ઠ𝕠p н𝖆 — пр𐐫т̠от𝐮пы ꫀׁׅܻ݊нд̠жυᩛׄн𝕒 🥹 . . . и тэ̠𝔁𝚎н𝖆 ? ? 🌲 ϐɕׄя̠ υнф𐐫𝚙м𝓪ц𝕦я в ӄִׄ𝖔мм. с𝓸∂ꫀׁׅܻ : ⚠️ ϐ𐐼ꉔӄִׄr𝐨o𝓶𝚜🥹𝚜𝓮ꫀׁׅ m𝕠r𝖊... ݁ 🎀 — ➿🔡➿🔡➿ ➿ — ₊ ⊹ ⠀ ❤️O5 : 55 🥹@unjectcg * 🌟

Channel
AUD | υn𝓳𝚎ɕׄ𝖙՚ wо̠𝐫𝖑∂
@unjectcg
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
49subscribers
+2 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 | -1003486609072 |
|---|---|
| Type | Channel |
| Username | @unjectcg |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/unjectcg |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 19:17 | 49 | +2 |
| 10 Aug 2026, 13:45 | 47 | no change |
| 7 Aug 2026, 03:16 | 47 | first reading |
Engagement
17 posts held, back to 15 June 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 34.7%
- avg views ÷ 49 subscribers
- Avg views / post
- 17.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 17 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 17 (15 June 2026 – 10 August 2026) |
| Views total | 34 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 13:45 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Video runtime
- 2m 44s
- Average length
- 2m 44s
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.
Reaction mix
47 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 21.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5246889613963846227 | 10 | 21.3% | |
| custom 5246938061194945854 | 7 | 14.9% | |
| custom 5247037227694842554 | 7 | 14.9% | |
| custom 5246964677107277993 | 6 | 12.8% | |
| custom 5246750169260647212 | 5 | 10.6% | |
| custom 5246824532324410673 | 5 | 10.6% | |
| custom 5247093985687659938 | 3 | 6.38% | |
| 🕊 | 3 | 6.38% | |
| 🤩 | 1 | 2.13% |
Custom emoji. 7 of the rows above are 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 6 of the 17 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 47reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 15 June 2026 to 10 August 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
Sticker, posted without a caption
Sticker, posted without a caption
File, posted without a caption
🤩𝘵h𝖊υᩛׄ 𐐼𝓻e lоoӄִׄιn𝚐 𝓪t . .🔤NʝЕ̠𝐂T ݁ 🎀 — ➿🔡➿🔡➿ ➿ — ₊ ⊹ ݁ ₊ ⊹ 🥹D🔤ϐ : υt 👁 🎀 ⠀🥹n𐐫 𝐬ꪱׁׁׁׅׅׅgη𝓪l 🌟݁ ₊ ⊹ #𝔒T5 🌟 🥹 🤩𝕡eɕׄ𝖎a𝘭 𝐅ꫀׁׅܻ݊αtυr𝘦𝖘 : 🥹 υnаνa𝐢𝚕aϐ𝓵ꫀׁׅܻ݊ # s𝓸𝐧g ⋮ Bꫀׁׅܻ݊∂ 𝙾f 𝕋h𐐫𝓻𝚗s — . . . ( orꪱׁׁׁׅׅׅ𝐠 ϐυᩛׄ tх̠𝚝 ) 🥹∂𝗲ϐυt с𝓸∂ꫀׁׅܻ : ⚠️ ϐ𐐼ꉔӄִׄr𝐨o𝓶𝚜🥹𝚜𝓮ꫀׁׅ m𝕠r𝖊... ݁ 🎀 — ➿🔡➿🔡➿ ➿ — ₊ ⊹ ⠀ ❤️O5 : 55 🥹@unjectcg * 🌟
custom 52467501692606472125custom 52468245323244106733custom 52469646771072779933custom 52468896139638462272custom 52470372276948425542🤩1
Sticker, posted without a caption
ㅤt𝐨∂𝓪υᩛׄ ݁ ๋ . 1𝟴:𝐎7̠ m𝖘𝓴
custom 52468896139638462272
Sticker, posted without a caption
Sticker, posted without a caption
Ветер Снова Приходит , Но Я Вырываюсь На Свободу
custom 52468896139638462274
Sticker, posted without a caption
Photo, posted without a caption
🕊3custom 52470939856876599382custom 52469646771072779931custom 52470372276948425541
Showing the 12 most recent of 17 posts we hold for @unjectcg. 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 — 739,634 of 1,549,376entries 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 2 registered channels — 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“AUD | υn𝓳𝚎ɕׄ𝖙՚ wо̠𝐫𝖑∂” (@unjectcg), 49 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/unjectcg.
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.