мой тупой тритип (точнее, мое виденье их) и тупо ральзе😂😂 #another
custom 54315871577456437741custom 54563018856254815911

Channel
@veuukji
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
84subscribers
+40 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004367807009 |
|---|---|
| Type | Channel |
| Username | @veuukji |
| Created | Between 1 June 2026 and 4 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/veuukji |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 23:57 | 84 | +18 |
| 9 Sept 2026, 18:20 | 66 | +6 |
| 30 Aug 2026, 22:02 | 60 | +3 |
| 24 Aug 2026, 10:08 | 57 | +4 |
| 16 Aug 2026, 20:46 | 53 | +9 |
| 10 Aug 2026, 16:00 | 44 | no change |
| 8 Aug 2026, 10:55 | 44 | first reading |
13 posts held, back to 4 August 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 13 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
138 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5431587157745643774 | 33 | 23.9% | |
| custom 5429282048797876367 | 27 | 19.6% | |
| custom 5454282933168783292 | 26 | 18.8% | |
| custom 5456301885625481591 | 23 | 16.7% | |
| custom 5429387593324211748 | 19 | 13.8% | |
| custom 5456568465655609059 | 10 | 7.25% |
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 are Telegram’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 13 of the 13 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 138 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 4 August 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.
мой тупой тритип (точнее, мое виденье их) и тупо ральзе😂😂 #another
custom 54315871577456437741custom 54563018856254815911
фоур из бфб мой любимый смотрите бесплатно я ему продумаю дизайн... когда-та... #bfb
custom 54292820487978763674custom 54315871577456437741
велики каллобарейшн с @q16444C06664L аля санкви #collaboration #oc
custom 54293875933242117483custom 54565684656556090592custom 54542829331687832921custom 54563018856254815911
короче привет и так я так подумал в щп и захотел брать кмм на скины (на арты не беру cuz у меня сейчас немного скачет стиль) крч 1 скин в майне = 200 рб/200 тг звезд ну а если вы нищие как и я, то могу сделать трейд аля скин за арт вам сделать ,если кто и хочет то мой лс @deinerlord / в коммы ?? не надеюсь на заказы but грех не попробовать и тд чуть позже напишу это в нав-ции актуально всегда потому что я хочу деньг…
custom 54565684656556090593custom 54563018856254815911
очень богато одарил рандома из тт #gift #skin
custom 54293875933242117486custom 54315871577456437745custom 54563018856254815914custom 54542829331687832922
вам машут 👀 #oc
custom 54292820487978763674custom 54293875933242117483custom 54315871577456437743
майн скин для @ewwqqn за арт👀 я вообще впервые делаю фурри, вообще буду учится делать меховую структуру рендера в таком 😉 #skin #trade
custom 54315871577456437743custom 54542829331687832922custom 54563018856254815912
майн скин для @Ukkii_i за 100 звёзд 😁 #skin #cmm (?)
custom 54315871577456437743custom 54542829331687832923custom 54293875933242117482custom 54563018856254815912custom 54292820487978763671
хэппи бездей теперь и моего браза батонна с зернадцать лет его☠☠ #gift
custom 54292820487978763675custom 54542829331687832925custom 54315871577456437744custom 54293875933242117481
скетч спч от скуки #another
custom 54292820487978763677custom 54542829331687832924custom 54563018856254815914
я забыл запостить с дере моего друна пикселя/ казла #gift
custom 54292820487978763676custom 54315871577456437746custom 54293875933242117484custom 54565684656556090591
AYO CHILLL привет я сделал скин грокса #skin #mcyt
custom 54315871577456437747custom 54542829331687832922custom 54563018856254815912
Showing the 12 most recent of 13 posts we hold for @veuukji. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“lord yawhoo” (@veuukji), 84 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/veuukji.
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.