Channel
@v1nrouge_ph
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
104subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001911679641 |
|---|---|
| Type | Channel |
| Username | @v1nrouge_ph |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/v1nrouge_ph |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 51% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 21:55 | 104 | +1 |
| 28 Aug 2026, 13:54 | 103 | +1 |
| 14 Aug 2026, 21:13 | 102 | +1 |
| 9 Aug 2026, 10:33 | 101 | no change |
| 7 Aug 2026, 19:44 | 101 | first reading |
3 posts held, back to 22 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 3 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
94 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 41.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5472351564230315674 | 39 | 41.5% | |
| custom 5303253706739828616 | 16 | 17.0% | |
| custom 5472275826777015274 | 15 | 16.0% | |
| custom 5472420245052341388 | 14 | 14.9% | |
| custom 5415734764168565862 | 7 | 7.45% | |
| custom 5440543036436132414 | 3 | 3.19% |
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 3 of the 3 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 94 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 22 June 2026 to 19 July 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.
алтай, июль 2026 nikon f100 / yes!star 200 прикольная пленка, я думала, что это кодак голд, но походу нет
custom 547235156423031567414custom 54722758267770152745custom 54724202450523413884custom 54405430364361324142custom 54157347641685658621
алтай, июль 2026 pentax 6x7 / kodak gold
custom 547235156423031567419custom 547227582677701527410custom 54157347641685658626custom 54405430364361324141custom 54724202450523413881
пока летних пленок нет, вспомню лето 2023 и нашу поездку на капчагай, алматы снято на pentacon six и kodak 5222
custom 530325370673982861616custom 54724202450523413889custom 54723515642303156746
Showing the 3 most recent of 3 posts we hold for @v1nrouge_ph. 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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“what i’m doing out of bed” (@v1nrouge_ph), 104 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/v1nrouge_ph.
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.