Channel

𝐁𝐋𝐔𝐄𝐏𝐑𝐈𝐍𝐓 𝐄𝐎 𝐆𝐀𝐋𝐋𝐄𝐑𝐘

@BPEOGALLERY

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

97subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID	-1001545591353
Type	Channel
Username	@BPEOGALLERY
Description	⚠️ WARNING ALLERT ALL PROPERTIES CREATED BY BLUEPRINT EO TEAM, STRICTLY PROHIBITED STEAL OR PLAGIARISM !!
Created	Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	9 August 2026
Last confirmed live	9 August 2026
Measurements held	2
On Telegram	t.me/BPEOGALLERY

Growth

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 96–98 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
9 Aug 2026, 12:01	97	no change
6 Aug 2026, 09:07	97	first reading

Engagement

5 posts held, back to 5 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 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days: 52.8%; avg views ÷ 97 subscribers
Avg views / post: 51.2; 5 posts measured
Reaction rate: —; this channel exposes no reaction counts
Posts in window: 5; of 5 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.

What these figures were computed from
Window	Rolling 30 days · latest post in window 8 August 2026
Posts held	5 (5 August 2026 – 8 August 2026)
Views total	256
Reactions total	—
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	9 Aug 2026, 12:01 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

Links: ≈1

Lifetime counters from Telegram’s own channel header, read 9 August 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.

Citation-graph rank

Citation-graph rank — 194,599 of 1,169,250entries 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.

HIBERNASI | ミ🌳 𝔈𝔠𝔥𝔞𝔫𝔠𝔦𝔞 𝔦𝔪𝔭𝔢𝔯𝔦𝔶𝔞 🇮🇹 彡
@EchanciaEmpire · 1,0181 post 𝗚𝗔𝗟𝗟𝗘𝗥𝗬 𝗢𝗙 𝗖𝗜𝗟𝗣𝗔𝗦𝗛𝗔𝗦𝗧𝗥𝗔
@GALLERYCSA · 1171 post (𝐎𝐏𝐄𝐍 𝐌𝐄𝐌𝐁𝐄𝐑) 𝐔𝐌𝐁𝐑𝐀 𝐍𝐎𝐂𝐓𝐈𝐒 𝐊𝐈𝐍𝐆𝐃𝐎𝐌
@OFFICIALUMBRA · 1,4051 post 𝕿𝗵𝗲 𝐒𝗲𝗮𝗹𝘁𝗵 𝕶𝗶𝗻𝗴𝗱𝗼𝗺
@SEALTHOFC · 1,1431 post

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

Named by

Channels on the register whose posts name this channel's handle.

OPBOOK AUG | 𝐁𝐋𝐔𝐄𝐏𝐑𝐈𝐍𝐓 𝐄𝐎
@BLUEPRINTOFC · 10,2866 posts VAKUM | 𝐇𝐎𝐔𝐒𝐄 𝐎𝐅 𝐉𝐔𝐒𝐓𝐈𝐂𝐈𝐀
@HOUSEOFJUSTICIA · 4,1504 posts 𝐎𝐅𝐂 𝐊𝐑𝐀𝐊𝐄𝐍𝐒
@OFCKRAKENS · 792 posts 𝟭𝟵𝟰𝟱 𝗖𝗢𝗥𝗣.
@official1945corp · 392 posts [ need racun ] 𝐕𝐄𝐍𝐎𝐌𝐈𝐑𝐄 𝐄𝐌𝐏𝐈𝐑𝐄
@VenomireOFC · 1,7052 posts 𝗚𝗔𝗟𝗟𝗘𝗥𝗬 𝗢𝗙 𝗖𝗜𝗟𝗣𝗔𝗦𝗛𝗔𝗦𝗧𝗥𝗔
@GALLERYCSA · 1171 post 𝐌𝐀𝐑𝐐𝐔𝐄𝐒𝐀 𝐃𝐄 𝐅𝐔𝐄𝐆𝐎
@MDERESTAURANT · 1,9321 post 𝐀𝐁𝐘𝐒𝐒 𝐎𝐂𝐄𝐀𝐍𝐈𝐂 𝐑𝐎𝐘𝐀𝐋 𝐀𝐂𝐀𝐃𝐄𝐌𝐘
@Ofc_VanguardImperial · 3091 post (𝐎𝐏𝐄𝐍 𝐌𝐄𝐌𝐁𝐄𝐑) 𝐔𝐌𝐁𝐑𝐀 𝐍𝐎𝐂𝐓𝐈𝐒 𝐊𝐈𝐍𝐆𝐃𝐎𝐌
@OFFICIALUMBRA · 1,4051 post [𝐂𝐋𝐎𝐒𝐄 𝐀𝐃𝐎𝐏𝐒𝐈] 𝐏𝐚𝐧𝐭𝐢 𝐀𝐬𝐮𝐡𝐚𝐧 𝐏𝐫𝐢𝐦𝐫𝐨𝐬𝐞 𝐕𝐚𝐥𝐥𝐞𝐲 𝐇𝐚𝐯𝐞𝐧
@PantiAsuhanPrimroseValleyHaven · 3,0271 post HIRSTAFF & OPBOOK | POTION EVENT ORGANIZER
@POTIONEO · 7,1031 post OPBOOK | STAR IDOL OFC
@STARIDOLOFC · 3,2121 post 𝐏𝐎𝐒𝐓𝐄𝐑 𝐒𝐖𝐀𝐍𝐋𝐀𝐊𝐄 𝐒𝐂.
@SWANLAKEPOSTER · 1,8491 post 𝘛𝘩𝘦 𝘣𝘰𝘹 𝘱𝘢𝘤𝘬𝘢𝘨𝘦 𝘤𝘰𝘶𝘳𝘪𝘦𝘳
@thebox_kurir · 241 post 𝐓𝐎𝐘𝐒𝐓𝐀𝐑 𝐊𝐈𝐍𝐃𝐄𝐑𝐆𝐀𝐑𝐓𝐄𝐍
@TOYSTAROFC · 2,5291 post 𝗩𝗘𝗗𝗔 𝗟𝗢𝗞𝗔 𝗛𝗜𝗚𝗛 𝗦𝗖𝗛𝗢𝗢𝗟 𝗢𝗙𝗙𝗜𝗖𝗜𝗔𝗟
@VECAHS_OFC · 3,1071 post

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

“𝐁𝐋𝐔𝐄𝐏𝐑𝐈𝐍𝐓 𝐄𝐎 𝐆𝐀𝐋𝐋𝐄𝐑𝐘” (@BPEOGALLERY), 97 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/BPEOGALLERY.

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.