Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗸𝗼𝗶 𝘀𝗵𝗼𝗽 ᶠᶦʳᵉ ˢʰᵒᵖ

Channel

𝗸𝗼𝗶 𝘀𝗵𝗼𝗽 ᶠᶦʳᵉ ˢʰᵒᵖ

@koishopi

2 usernames

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

491subscribers

+225 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003733883176
TypeChannel
Usernames@FIREADOPTSHOP @koishopi
DescriptionМагазин для продажи творчества!! Art by: @kkkywy
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 November 2026
Measurements held11
On Telegramt.me/koishopi

Topic

Gaming — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 41% 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

34912478 August 2026 — 266 subscribers9 August 2026 — 265 subscribers16 August 2026 — 277 subscribers25 August 2026 — 282 subscribers1 September 2026 — 293 subscribers10 September 2026 — 302 subscribers18 September 2026 — 307 subscribers6 October 2026 — 4 subscribers6 November 2026 — 3 subscribers17 November 2026 — 491 subscribers17 November 2026 — 491 subscribers8 August 202617 November 2026
11 measurements spanning 101 days, net +225. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Nov 2026, 10:22491no change
17 Nov 2026, 09:47491+488
6 Nov 2026, 21:383-1
6 Oct 2026, 20:204-303
18 Sept 2026, 03:38307+5
10 Sept 2026, 18:15302+9
1 Sept 2026, 04:05293+11
25 Aug 2026, 03:28282+5
16 Aug 2026, 20:03277+12
9 Aug 2026, 10:07265-1
8 Aug 2026, 14:15266first reading

Engagement

23 posts held, back to 7 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 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
11.7%
avg views ÷ 491 subscribers
Avg views / post
57.5
12 posts measured
Reaction rate
2.70%
reactions ÷ views · ER floor
Posts in window
12
of 23 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 3 of 12 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 17 November 2026
Posts held23 (7 August 2026 – 17 November 2026)
Views total690
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 10:22 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

Photos
≈1,310
Videos
≈26
Links
≈301

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

8 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💘450.0%
🔥337.5%
❤‍🔥112.5%

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

Measured over the 23 most recent posts we hold, published 7 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 0 of 12 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

17 Nov 2026, 08:32 UTC22 views1 reactionsread 17 November 2026

🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧 🤩Акт ставка – 500₽! Успейте приобрести сочный ючик

💘1

16 Nov 2026, 17:02 UTC47 viewsread 17 November 2026
Photo

☆МНОГОСЛОТНЫЙ ЮЧ☆ Пока возьму 3 слота на этот ючик🍒 Можно выбрать и с одеждой и без, фулл в комментариях 🎀 Фикс1: 850р (не меняю телосложение) Фикс2: 1100 (меняю телосложение) Рисую девушек/парней/антро, могу попробовать фури Не рисую гуро Бронь 2 дня Отрисовка 1 юча неделю за фикс1, 2 недели фикс2. В порядке очереди Правила: не присваивать авторство Оплата: сбер, т банк, lava top, каспи Слотики можете заним…

16 Nov 2026, 14:34 UTC58 viewsread 17 November 2026
Photo

🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧 🤩Акт ставка на кастом – 100₽!!

16 Nov 2026, 13:32 UTC62 views1 reactionsread 17 November 2026
Photo

🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧 🤩Свободные слотики на милые комишки ждут вас!!

💘1

16 Nov 2026, 13:01 UTC64 views2 reactionsread 17 November 2026
Photo

YCH BICEPS HEART💝💪 1 СЛОТ 🤍 НАЧ:500р 🤍 МИН:- 🤍 АВТО:2000р за авто: нет доплат(о них ниже); дополнительно присылаю персонажей вместе и по отдельности; Дд 10 дней ~Доплаты: Заменить девушку на парня 150р Смена эмоции 0р Смена позы 200р(только на хед/халф) ~Конец: через 24ч ппс ~Оплата: сбербанк ~Дд: 2 недели ~Бронь до 2х дней ~НЕ рисую: старики, фурри с длинными мордочками, остальное спрашиваете 🤍 ЛС …

💘2

16 Nov 2026, 12:03 UTC64 viewsread 17 November 2026
Photo

АУКЦИОН на скетчеви кастом реф как на примерах нач - дар мин - 50 авто - нету конец аукциона через 48ч ппс или досрочно ДД неделя оплата :: сбер/сбп; можно частями рисую :: людей/чиби/пони/антро не рисую :: роботов, нсфв, жеское гуро мой тгк :: @hdsknn ЛС :: @VENusima1 #koi_ven #koi_аук #koi_кастом

16 Nov 2026, 10:33 UTC69 viewsread 17 November 2026
Photo

🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧🫧 🤩Акт – 650₽!!

16 Nov 2026, 09:04 UTC70 viewsread 17 November 2026
Photo

🦋🔠🔠🔠🔠🔠🎐(перезалив) 💬💬💬💬💬💬💬 Скетч/фулл, рубли и звезды Хед 100/200 50/100зв Халф 150/300₽ 70/180зв Фуллбоди 200/350₽ 100/200зв Чиби: 300₽ 180зв Доп инфа: Фон: +20-35% (градиент: +0%) Доп перс: +70% Нсфв: +60% Кастом/Реф: 400/550₽ 230/300зв Не рисую: Фералов, меха, пожилых, детализацию, жесткое гуро, качков, проблематику  🤩🤩🤩 🤩🤩 писать: @kykyk158 🤩🤩 дд: 1-2 недели Бронь 4 дня макс Оплата: 💳/💳/💳 #koi_K…

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

Forward network

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 8 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.

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

“𝗸𝗼𝗶 𝘀𝗵𝗼𝗽 ᶠᶦʳᵉ ˢʰᵒᵖ” (@koishopi), 491 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/koishopi.

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.