Photo, posted without a caption
❤8custom 54495250972472934572custom 54497869141586890221
Signed Виктор

Channel
@Uitek
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
124subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003845834615 |
|---|---|
| Type | Channel |
| Username | @Uitek |
| Created | Between 1 February 2026 and 13 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/Uitek |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 04:20 | 124 | +3 |
| 29 Aug 2026, 07:04 | 121 | +3 |
| 23 Aug 2026, 05:25 | 118 | -2 |
| 15 Aug 2026, 11:56 | 120 | -6 |
| 9 Aug 2026, 02:16 | 126 | no change |
| 7 Aug 2026, 03:16 | 126 | first reading |
18 posts held, back to 13 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 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 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
501 reactions across 18 posts, in 13 distinct kinds. The most used accounts for 41.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 206 | 41.1% | |
| custom 5449786914158689022 | 72 | 14.4% | |
| custom 6208636970264955676 | 48 | 9.58% | |
| custom 5449525097247293457 | 34 | 6.79% | |
| custom 5332398865184214455 | 33 | 6.59% | |
| custom 6228589163529111695 | 27 | 5.39% | |
| custom 5440516725466491965 | 24 | 4.79% | |
| custom 5449730693036784569 | 20 | 3.99% | |
| custom 6082306490142558133 | 15 | 2.99% | |
| custom 5298888581153065860 | 9 | 1.80% | |
| custom 5179170486650668001 | 7 | 1.40% | |
| custom 5215291818740053475 | 4 | 0.798% | |
| custom 5257968323190085675 | 2 | 0.399% |
Custom emoji. 12 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 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 18 of the 18 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 501 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 13 June 2026 to 7 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.
Photo, posted without a caption
❤8custom 54495250972472934572custom 54497869141586890221
Signed Виктор
Рисунков не будет
❤6custom 54497869141586890222custom 54495250972472934571
Signed Виктор
Иногда он ходит по своему шато в одних только капроновых чулках и приказывает слугам опускать взгляд как только он заходит в комнату в таком виде
❤18custom 54495250972472934574custom 54497869141586890223
Signed Виктор
Боц прокурор и за 19 лет работы провел 3115 дел, после чего ушёл в отставку
❤16custom 54497869141586890225custom 54495250972472934574
Signed Виктор
Это трейд с @snoogenss
❤12custom 54495250972472934572
Signed Виктор
Господин Боц не видит ничего плохого в понуждении слуг всегда облизывать дверную ручку его рабочего кабинета обработанной раствором денатония бензоата
❤14custom 54497869141586890228custom 54495250972472934576
Signed Виктор
Photo, posted without a caption
❤17custom 54497869141586890226custom 54495250972472934575
Signed Виктор
Ладно на
❤19custom 54495250972472934576custom 54497869141586890226
Signed Виктор
Все
❤26custom 54497869141586890225
Signed Виктор
Всех с днем MANGO
❤23custom 62285891635291116957custom 54497869141586890225custom 54495250972472934571
Signed Виктор
спокойной ночи
custom 544051672546649196524custom 620863697026495567611❤5
Signed Виктор Харассмен
Photo, posted without a caption
❤13custom 620863697026495567610custom 60823064901425581338custom 53323988651842144554custom 52988885811530658602custom 54497869141586890222custom 62285891635291116952custom 52579683231900856751
Signed Виктор Харассмен
Showing the 12 most recent of 18 posts we hold for @Uitek. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“5. SS-Panzer-Division „Wiking“” (@Uitek), 124 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/Uitek.
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.