Telegram RegisterThe public register of Telegram
Telegram profile photo for Fight For Bloody Throne Shop

Channel

Fight For Bloody Throne Shop

@FFBT_Shop

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

16subscribers

-1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002250053135
TypeChannel
Username@FFBT_Shop
Created5 December 2024 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live8 October 2026
Measurements held3
Confirmed unchanged4 times, most recently 8 October 2026
On Telegramt.me/FFBT_Shop

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 1 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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.

Growth

161716.511 August 2026 — 17 subscribers11 August 2026 — 17 subscribers3 September 2026 — 16 subscribers11 August 20263 September 2026
3 measurements spanning 23 days, net -1. 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 16–17 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 09:3516-1
11 Aug 2026, 20:4617no change
11 Aug 2026, 10:4917first reading

Engagement

5 posts held, back to 5 December 2024 — 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 5 posts for this entry, the most recent from 21 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

10 reactions across 1 post, in 3 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🖕660.0%
👍220.0%
🗿220.0%

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

Measured over the 5 most recent posts we hold, published 5 December 2024 to 21 July 2025, 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

21 Jul 2025, 19:56 UTC161 viewsread 11 August 2026
Photo

👥 نیروهای زمینی – 3000 جنگجوی مرگبار: 🛡️ 500 انسالید 🐎 500 سواره‌نظام ویل 🐉 500 شوالیه‌ی اژدها 🏹 500 نیزه‌دار دورنی 🎯 500 کراسبودار یکی دیگه انتخابی 🛠️ ادوات – 20 ابزار 🔥 10 × منجنیق سنگین 🎯 5 × اسکورپ 🧱 3 × دژکوب فولادی 🪜 2 × نردبان 🚢 ناوگان دریایی – 10 کشتی بلادی هیچ محدودیتی برای خرید نداره غلات مصرفی ندارن قیمت: 200 تخفیف 50%

21 Jul 2025, 19:56 UTC153 viewsread 11 August 2026
Photo

🏰 منابع عمرانی: 💰 70000 سکه 🪵 10000 چوب 🧱 10000 سنگ ⛏️ 7000 آهن 🍷 منابع خوراکی: 🍷 3000 شراب 🐟 3000 واحد ماهی 🍖 3000 واحد گوشت 🍎 3000 واحد میوه‌ 🩶 ویژگی‌ها و مزایا: 100 کردن محبوبیت قلعه شما قیمت: 500 هزار 😊 هیچ محدودیتی برای خرید ندارن

14 Jul 2025, 12:09 UTC160 views10 reactionsread 11 August 2026
Photo

📦 بسته‌های منابع: 💰 سکه: ۷۰۰۰ 🪵 چوب: ۱۰۰۰ 🧱 سنگ: ۱۰۰۰ 🔩 آهن: ۱۰۰۰ 🐠 ماهی: ۵۰۰ 🥩 گوشت: ۵۰۰ 💸 قیمت هر بسته: ۱۰ هزار تومان 🛒 انتخاب آزاد! مثلاً: ۲ گوشت، ۳ آهن، ۵ سکه 🎁 جایزه ویژه: هر کسی که ۱۰ بسته یا بیشتر بخره، ۲ آیتم رایگان هم جایزه می‌گیره 🎉 برای خرید پیام بدید ✅

🖕6👍2🗿2

Showing the 5 most recent of 5 posts we hold for @FFBT_Shop. 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.

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

“Fight For Bloody Throne Shop” (@FFBT_Shop), 16 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/FFBT_Shop.

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.