Telegram RegisterThe public register of Telegram

Channel

Seven Bigle

@SevenBigle

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

31subscribers

+0 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-1002671811297
TypeChannel
Username@SevenBigle
CreatedBetween 1 March 2025 and 8 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/SevenBigle

Growth

317 August 2026 — 31 subscribers11 August 2026 — 31 subscribers7 August 202611 August 2026
2 measurements spanning 3 days. 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 30–32 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 03:1631no change
7 Aug 2026, 16:0931first reading

Engagement

18 posts held, back to 8 July 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 20 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
71
Links
6

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

7 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👾228.6%
🔥228.6%
😭228.6%
114.3%

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

Measured over the 18 most recent posts we hold, published 8 July 2025 to 20 December 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

20 Dec 2025, 14:29 UTC40 viewsread 11 August 2026
Photo

Слив прака против NA1B Нт парням удачи и мы не расстраиваемся дальше больше #GOGO7BGL

20 Dec 2025, 13:51 UTC24 viewsread 11 August 2026
Photo

•⚔️• Format: Bo1 Mr12 •⌚• Time: 17:00 •🗺️• Map:Province •🔰• Tag:NA1B •🛡️• Side:T •Capitan•@tgkwantaqa Пожелайте нам удачи 🍀

20 Dec 2025, 13:45 UTC21 viewsread 11 August 2026
Photo

•⚔️• Format: Bo1 Mr12 •⌚• Time: 18:00 •🗺️• Map:Rust •🔰• Tag:kOshm •🛡️• Side:KT •Capitan•@yordergmd Пожелайте нам удачи 🍀

7 Dec 2025, 14:26 UTC40 viewsread 11 August 2026
Photo

Сыграли на турнире SHELL EPIC Выграли по картам 2:0 формат был:BO2 MVP: 18/4/12 Yuki-Rust MVP:22/1/18 WarkeN[C]-Zone 7 Спасибо парням за игру всем удачи #GOGO7BGL

7 Dec 2025, 10:30 UTC38 viewsread 11 August 2026
Photo

•⚔️• Format: Bo2 Mr12 •⌚• Time: 16:00 •🗺️• Map:Rust •🔰• Tag:ZV_20 •🛡️• Side:T •Capitan•@Solostr •⚔️• Format: Bo2 Mr12 •⌚• Time: 17:00 •🗺️• Map:Zone 7 •🔰• Tag:ZV_20 •🛡️• Side:KT •Capitan•@Solostr Пожелайте нам удачи 🍀

5 Dec 2025, 14:29 UTC36 viewsread 11 August 2026

Сегодня у нас отдых 🛌 всем удачи ждите завтра новостей #GOGO7BGL

4 Dec 2025, 15:50 UTC38 views2 reactionsread 11 August 2026
Photo

Первая катка против SHLYT хорошо наша команда отыграла я рад,что на провинции лучше себя чувствуют спасибо парням и SHLYT клану за прак в формате а на Hanami расслабились очень сильно,но по картам 1:1 Ничья #GOGO7BGL спасибо ждите новостей Mvp:ForS 22/14-Hanami Mvp:18/2/3 Wenkyy-Province Всем удачи 🍀

🔥2

4 Dec 2025, 13:36 UTC38 viewsread 11 August 2026
Photo

•⚔️• Format: Bo2 Mr12 •⌚• Time: 17:00 •🗺️• Map:Province •🔰• Tag:SHLYT •🛡️• Side:T •Capitan•@Shellxfurios •⚔️• Format: Bo2 Mr12 •⌚• Time: 18:00 •🗺️• Map:Hanami •🔰• Tag:SHLYT •🛡️• Side:KT •Capitan•@Shellxfurios Пожелайте нам удачи 🍀

3 Dec 2025, 14:53 UTC32 viewsread 11 August 2026
Photo

Сыграли против них прак хорошие типы достойно играют,а так нт проиграли бывает RVSTT #GOGO7BGL MVP:WarkeN[С] 20/6/19 Парням спасибо за хорошую игру Ждите новостей дамы и господа

3 Dec 2025, 12:20 UTC44 views2 reactionsread 11 August 2026
Photo

•⚔️• Format: Bo1 Mr12 •⌚• Time: 17:00 •🗺️• Map:Province •🔰• Tag:RVSTT •🛡️• Side:T •Capitan• @dontPsyhoz Пожелайте нам удачи 🍀

👾2

3 Dec 2025, 11:54 UTC35 views1 reactionsread 11 August 2026
Photo

•⚔️• Format: Bo1 Mr12 •⌚• Time: 18:00 •🗺️• Map:Hanami •🔰• Tag:RSB5 •🛡️• Side:T •Capitan• @The_L1ch Пожелайте нам удачи 🍀

1

3 Dec 2025, 04:36 UTC56 viewsread 11 August 2026

📍TIME TABLE📍 3.11.25 TEAM: Seven Bigle TAG:7BGL Search practice game Ищут праки •⚔️• Format: Bo1 Mr12 [❌] •⌚• Time: 17:00 •🗺️• Map: •🔰• Tag: •🛡️• Side: •⚔️• Format: Bo1 Mr12 [❌] •⌚• Time: 18:00 •🗺️• Map: •🔰• Tag: •🛡️• Side: •⚔️• Format: Bo1 Mr12 [❌] •⌚• Time: 19:00 •🗺️• Map: •🔰• Tag: •🛡️• Side: Found: [✅] Not found: [❌] Лс: @SN_MEN

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

Mentions

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

“Seven Bigle” (@SevenBigle), 31 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/SevenBigle.

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.