Telegram RegisterThe public register of Telegram
Telegram profile photo for PinkTrip

Channel

PinkTrip

@yanapinktrip

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

901subscribers

+54 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-1001721682094
TypeChannel
Username@yanapinktrip
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 October 2026
Measurements held13
Confirmed unchanged1 time, most recently 30 October 2026
On Telegramt.me/yanapinktrip

Topic

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 the other topics.

Growth

8459018737 August 2026 — 847 subscribers8 August 2026 — 847 subscribers8 August 2026 — 845 subscribers16 August 2026 — 856 subscribers24 August 2026 — 861 subscribers30 August 2026 — 873 subscribers7 September 2026 — 869 subscribers16 September 2026 — 875 subscribers30 September 2026 — 881 subscribers9 October 2026 — 887 subscribers15 October 2026 — 894 subscribers23 October 2026 — 899 subscribers30 October 2026 — 901 subscribers7 August 202630 October 2026
13 measurements spanning 84 days, net +54. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 837–909 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Oct 2026, 20:58901+2
23 Oct 2026, 02:00899+5
15 Oct 2026, 22:45894+7
9 Oct 2026, 18:01887+6
30 Sept 2026, 02:16881+6
16 Sept 2026, 05:59875+6
7 Sept 2026, 21:55869-4
30 Aug 2026, 00:23873+12
24 Aug 2026, 01:29861+5
16 Aug 2026, 21:27856+11
8 Aug 2026, 22:28845-2
8 Aug 2026, 01:19847no change
7 Aug 2026, 23:01847first reading

Engagement

16 posts held, back to 25 July 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 16 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
41s
Average length
21s

Measured directly from 2 videos 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

289 reactions across 15 posts, in 5 distinct kinds. The most used accounts for 26.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53638820320258490987626.3%
custom 54337676095625780287526.0%
custom 52493840364800781387325.3%
custom 54337348733218496984314.9%
custom 5249480694719072720227.61%

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 15 of the 16 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 289 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 25 July 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.

Telegram Stars

Stars received
14
across the posts below
Posts paid on
12
of 16 we hold a reading for · 75%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yanapinktrip. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 16 most recent posts we hold for this entry, published 25 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 17:13 UTC146 views15 reactions1 Starread 8 August 2026
Video message

Video message, posted without a caption

custom 52493840364800781389custom 53638820320258490982custom 54337676095625780282custom 52494806947190727201custom 54337348733218496981

6 Aug 2026, 16:49 UTC302 views13 reactionsread 8 August 2026

Чучуть на караокерном сегодня

custom 53638820320258490987custom 52493840364800781383custom 54337676095625780283

6 Aug 2026, 16:49 UTC351 views13 reactions2 Starsread 8 August 2026
Video message

Video message, posted without a caption

custom 52493840364800781386custom 53638820320258490985custom 54337676095625780282

5 Aug 2026, 14:07 UTC382 views13 reactions1 Starread 8 August 2026
Photo

Как же круто это было емае

custom 53638820320258490989custom 52494806947190727203custom 54337676095625780281

5 Aug 2026, 07:14 UTC400 views10 reactions1 Starread 8 August 2026
Video message

Video message, posted without a caption

custom 524938403648007813810

3 Aug 2026, 11:20 UTC515 viewsread 8 August 2026

Кстати, у кого есть контент со вчера, накидайте в комментариях🌚

3 Aug 2026, 11:19 UTC514 views4 reactionsread 8 August 2026

Друзья, кто был вчера на настолках и планирует ещё посещать подобные мероприятия, добавляйтесь в беседу сигмы, там будут анонсы https://t.me/n_a_s_t_o_l_k_i

custom 52493840364800781384

2 Aug 2026, 11:53 UTC547 views19 reactions2 Starsread 8 August 2026
Video message

Video message, posted without a caption

custom 524938403648007813810custom 54337676095625780285custom 52494806947190727204

2 Aug 2026, 09:22 UTC539 views25 reactions1 Starread 8 August 2026
Video message

Video message, posted without a caption

custom 543376760956257802819custom 52493840364800781386

2 Aug 2026, 04:11 UTC586 views40 reactions1 Starread 8 August 2026
Photo

Я снова в праймике

custom 543376760956257802823custom 536388203202584909811custom 52494806947190727205custom 52493840364800781381

2 Aug 2026, 00:15 UTC588 views14 reactions1 Starread 8 August 2026

Все помнят?

custom 52493840364800781389custom 52494806947190727202custom 53638820320258490982custom 54337676095625780281

29 Jul 2026, 16:15 UTC840 views41 reactions1 Starread 8 August 2026
Photo

Это супер мили Несси

custom 536388203202584909820custom 543376760956257802812custom 54337348733218496985custom 52493840364800781383custom 52494806947190727201

Showing the 12 most recent of 16 posts we hold for @yanapinktrip. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

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.

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.

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.

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 30 October 2026 — this entry's latest reading, not the date you are reading this.

“PinkTrip” (@yanapinktrip), 901 subscribers as measured 30 October 2026. Telegram Register, tgregister.com/channel/yanapinktrip.

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.