Channel
@bloodbrx98
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
277subscribers
-20 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003746160648 |
|---|---|
| Type | Channel |
| Username | @bloodbrx98 |
| Created | Between 1 February 2026 and 23 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/bloodbrx98 |
Other / unclassifiable — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 07:36 | 277 | -6 |
| 10 Sept 2026, 08:40 | 283 | -9 |
| 31 Aug 2026, 06:43 | 292 | -5 |
| 23 Aug 2026, 16:39 | 297 | -3 |
| 15 Aug 2026, 16:48 | 300 | +3 |
| 8 Aug 2026, 08:03 | 297 | no change |
| 8 Aug 2026, 00:17 | 297 | first reading |
19 posts held, back to 23 June 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 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 19 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
https://jwt-rho-rose.vercel.app/access?eat=10cb5d1f8bdc2cc47044d456992d5b75a4159b04c2938ae44df75272768e1580794e06413423dd43858f9da016a5b81c6a13a6454b9460e0c48b7045338d90720d9cdd7d0e26194bbe0f4aa396c986e0 Eat to access Access to jwt One in one ✅
HLLWW GUYS 🦋 NEED BLUESTACKS GUEST LOGIN? 🙂 ANY ONE NEED TO DM @brxonly
Photo, posted without a caption
Only 2 slots left price 700₹ bargaining = instant block
💍Selling Coloured Nickname With CraftLand 60k+ Points In Low Price 💬Dm : @vaibhavff570 🌩Grab Before Gone Because Only For 7 Users Limited Slot Also You Will Get It Instantly No Delay 🇮🇳Upi And Binance Both Accepted ✅ Only For India🇮🇳 Server
💍Selling Coloured Nickname With CraftLand 60k+ Points In Low Price 💬Dm : @vaibhavff570 🌩Grab Before Gone Because Only For 7 Users Limited Slot Also You Will Get It Instantly No Delay 🇮🇳Upi And Binance Both Accepted ✅ Only For India🇮🇳 Server
https://brx-api.lovable.app/ 🦋🤍 Adding more something's neww
Server now Change Access token Jwt eat added + access token https://brx-api.lovable.app/
import requests url = "https://clientbp.ggpolarbear.com/DrawSharedGacha" token = input("Enter JWT Token: ") headers = { "User-Agent": "Dalvik/2.1.0 (Linux; U; Android 9; ASUS_Z01QD Build/PI)", "Connection": "Keep-Alive", "Accept-Encoding": "gzip", "Authorization": f"Bearer {token}", "Content-Type": "application/x-www-form-urlencoded", "Expect": "100-continue", "X-Unity-Version": "2018.4…
https://jwt-rho-rose.vercel.app/access?eat=10cb5d1f8bdc2cc47044d456992d5b75a4159b04c2938ae44df75272768e1580794e06413423dd43858f9da016a5b81c6a13a6454b9460e0c48b7045338d90720d9cdd7d0e26194bbe0f4aa396c986e0 { "account_name": "ᴀᴅᴍɪɴ•Raihan", "account_id": 14209703830, "platform": "Google", "region": "BD", "access_token": "85d1158933084b7c08be8d24536154f35eeba7b64c7d77f6f1927904d79ec1bf", "open_id": "cbe…
Channel name was changed to «BRX API»
File, posted without a caption
Showing the 12 most recent of 19 posts we hold for @bloodbrx98. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“BRX API” (@bloodbrx98), 277 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bloodbrx98.
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.