Telegram RegisterThe public register of Telegram
Telegram profile photo for Pinky Bar: Genshin impact

Channel

Pinky Bar: Genshin impact

@pinkybar_coffee

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

64subscribers

+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-1003972694120
TypeChannel
Username@pinkybar_coffee
CreatedBetween 1 April 2026 and 10 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/pinkybar_coffee

Growth

6264637 August 2026 — 62 subscribers10 August 2026 — 62 subscribers15 August 2026 — 64 subscribers7 August 202615 August 2026
3 measurements spanning 8 days, net +2. 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 62–64 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 08:4464+2
10 Aug 2026, 04:1562no change
7 Aug 2026, 03:0162first reading

Engagement

16 posts held, back to 10 July 2026the 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
296.7%
avg views ÷ 64 subscribers
Avg views / post
190
14 posts measured
Reaction rate
9.48%
reactions ÷ views · ER floor
Posts in window
14
of 16 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. It is computed over the 13 of 14 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held16 (10 July 20269 August 2026)
Views total2,658
Reactions total228
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 04:15 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
1m 55s
Average length
16s

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

245 reactions across 15 posts, in 10 distinct kinds. The most used accounts for 53.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 525801113542409674513053.1%
4116.7%
🖕218.57%
💔156.12%
🗿145.71%
🔥83.27%
🥱62.45%
👍52.04%
🕊31.22%
🤯20.816%

Custom emoji. One 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 count beside it isTelegram’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 245reactions 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 10 July 2026 to 9 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

9 Aug 2026, 16:29 UTC55 views8 reactionsread 10 August 2026

🤩Ивент закончился 🤩 Под этим постом можете присылать фотографии с ивента. Так же поделиться тем, какие напитки понравились больше всего ❤️

custom 52580111354240967458

9 Aug 2026, 11:37 UTC61 views9 reactionsread 10 August 2026
Photo

🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 Сегодня последний день ивента. Косплееры будут с 15 до 18🤩 Успейте пройти интерактивы и попробовать наши напитки🤩 Так же посмотрите какую красоту нам нарисовали за эти дни. Узнали свои рисунки?

custom 52580111354240967459

8 Aug 2026, 21:53 UTC83 views10 reactionsread 10 August 2026
Photo

🩹🩹🩹🩹🩹🩹 🩹🩹🩹 Спасибо всем, кто пришёл 🤩 Завтра наш ивент подходит к концу. Успейте прийти ❤️ Колумбина Варка Лаума(косплеер специально сделал образ в стиле нашей кофейни так что это наш маскот) Флинс

custom 525801113542409674510

8 Aug 2026, 08:47 UTC77 views6 reactionsread 10 August 2026
Video

🤩Старт второго дня начался🤩 Обязательно приходите попробовать вкусные напитки и пройти интерактивы у наших косплееров💕

custom 52580111354240967456

7 Aug 2026, 20:07 UTC179 views13 reactionsread 10 August 2026
Video

🩹🩹🩹 🩹🩹🩹 Первый день ивента пролетел. Спасибо каждому, кто заглянул – мы очень рады, что вы с нами. Ждём вас в оставшиеся дни💕

custom 525801113542409674513

7 Aug 2026, 08:26 UTC104 views15 reactionsread 10 August 2026
Photo

Всем доброго дня 💖 Кофейня уже готова принимать гостей. Будем ждать вас на ивенте💕

custom 525801113542409674515

6 Aug 2026, 17:01 UTC122 views10 reactionsread 10 August 2026
Photo

Так же вы сможете увидеть этих прекрасных дам на этих выходных 🩷 🗿Лаума 🗿Колумбина

custom 525801113542409674510

6 Aug 2026, 08:55 UTC111 views11 reactionsread 10 August 2026

💖Косплееры будут на ивенте все три дня с 15-19💖 Приходите. Будем рады каждому🩷

custom 525801113542409674511

1 Aug 2026, 20:57 UTC188 views11 reactionsread 10 August 2026
Video

Всем привет ✨ Есть важное обновление: наш ивент по Genshin Impact переносится на новую локацию! Теперь встречаемся в кофейне «Веранда» по адресу: бульвар Энгельса, 14А Не теряйтесь, сохраняйте новый адрес и приходите за атмосферой, вкусным кофе и вайбом Genshin 💫

custom 525801113542409674511

29 Jul 2026, 12:10 UTC240 views35 reactionsread 10 August 2026
Video

🤩Завершаем наш релиз🤩 ✨Колумбина – «Лунная дева» Молочный коктейль с мороженым и нежными взбитыми сливками. Голубой оттенок, кокосовая нотка и лёгкая ваниль. Напиток, который пьют под светом луны. Один из напитков будет для вас сюрпризом, который вы уже сможете попробовать воочию на ивенте

🖕129💔7🕊3🔥2custom 52580111354240967452

28 Jul 2026, 07:49 UTC241 views33 reactionsread 10 August 2026
Video

🤩Встречаем следующий напиток и косплеера🤩 ✨ Дотторе — «Сегмент» Слоистый напиток-эксперимент: ягодная глубина, голубое сияние и хрустальный холод. Два слоя – две стороны личности Доктора.

🗿147custom 52580111354240967456💔3🥱2🖕1

27 Jul 2026, 10:29 UTC475 views33 reactionsread 10 August 2026
Video

🤩Продолжаем представлять наши напитки и косплееров🤩 ✨Флинс «Светоч Клятвы» Холодный кофе с молоком, лавандово-дымным сиропом. Свет во тьме, который можно попробовать на вкус. Энергия стража, застывшая в слоях льда и сияния. Кого хотите увидеть следующим?

12🖕8🔥4🥱4custom 52580111354240967453💔2

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

22 Jul 2026, 09:40 UTCAnonymous Poll53 voters

Привет! Мы готовимся к ивенту и хотим понять, сколько человек планирует прийти. Это поможет нам подготовить количество напитков, призов и мерча

  1. Планирую прийти40%
  2. Возможно, приду30%
  3. Не смогу прийти25%
  4. Приду с компанией (в комментариях можете написать сколько человек)21%

The shares total 116%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 16 most recent posts we hold, published 10 July 2026 to 9 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 145,793 of 1,480,944entries 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.

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

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.

“Pinky Bar: Genshin impact” (@pinkybar_coffee), 64 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/pinkybar_coffee.

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.