🌳 ini kenapa ya biz??

Channel
BIZFESS 🌳
@Bizfess
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
17,629subscribers
+4,089 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1003873352647 |
|---|---|
| Type | Channel |
| Username | @Bizfess |
| Description | GW CAPEK BGT JADI SELLERRRRRRR, TAPI GW CINTA DUIT. Daripada ngebatin mulu ya kan jadi seller, mending curhat di @bizfess. Base khusus anak BA! Buyer dan Seller semuanya boleh curhat dN bertanya. 🌳 as Trigger Send @BizFessBot. Handle, @BizFessCT |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/Bizfess |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 08:55 | 17,629 | +1 |
| 9 Nov 2026, 14:35 | 17,628 | +13 |
| 8 Nov 2026, 09:05 | 17,615 | +38 |
| 7 Nov 2026, 01:19 | 17,577 | +6 |
| 6 Nov 2026, 03:04 | 17,571 | +18 |
| 4 Nov 2026, 23:04 | 17,553 | +31 |
| 3 Nov 2026, 21:19 | 17,522 | +13 |
| 2 Nov 2026, 20:56 | 17,509 | +23 |
| 1 Nov 2026, 22:16 | 17,486 | +15 |
| 31 Oct 2026, 19:56 | 17,471 | +17 |
| 30 Oct 2026, 17:58 | 17,454 | +62 |
| 29 Oct 2026, 18:41 | 17,392 | +27 |
| 28 Oct 2026, 19:48 | 17,365 | +11 |
| 27 Oct 2026, 17:44 | 17,354 | +22 |
| 26 Oct 2026, 18:30 | 17,332 | +24 |
| 25 Oct 2026, 20:36 | 17,308 | +47 |
| 24 Oct 2026, 17:20 | 17,261 | +5 |
| 23 Oct 2026, 17:30 | 17,256 | +13 |
| 22 Oct 2026, 20:30 | 17,243 | +17 |
| 21 Oct 2026, 15:57 | 17,226 | first reading |
Engagement
1,389 posts held, back to 6 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 71 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.545%
- avg views ÷ 17,629 subscribers
- Avg views / post
- 96.0
- 380 posts measured
- Reaction rate
- 2.54%
- reactions ÷ views · ER floor
- Posts in window
- 380
- of 1,389 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 55 of 380 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 1,389 (6 August 2026 – 12 November 2026) |
| Views total | 36,479 |
| Reactions total | 150 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 05:00 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
- ≈4,970
- Videos
- ≈33
- Links
- ≈837
Lifetime counters from Telegram’s own channel header, read 12 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.
- Video runtime
- 39s
- Average length
- 20s
Measured directly from 2 videos 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.
Reaction mix
649 reactions across 105 posts, in 7 distinct kinds. The most used accounts for 46.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 304 | 46.8% | |
| 💯 | 126 | 19.4% | |
| ❤ | 121 | 18.6% | |
| 🕊 | 82 | 12.6% | |
| ⚡ | 8 | 1.23% | |
| 💘 | 6 | 0.924% | |
| 🍓 | 2 | 0.308% |
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 129 of the 1,000 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 649 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 17 August 2026 to 12 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 380 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).
🌳 abis nyidukin ubot, lapor ke store yg dipromosiin WKWK PUAS BGT RASANYA
🌳 bizz mau nanya kalau aku kan sis p kan ke reseller, nah tp take sgmail fresh, cuma lg ke non/bermasalah gmailnya, tp pemulihan udah di pasang sebelum problem, kira kira ini duitnya bisa ttp ke tf ga ke aku nantinya? atau gimana.. kalau masih problem jujur aku butuh duitnya sih😭
🌳 sumpahh dana ni kenapa masalah mulu sii, jantung gw udah mau pindah ke usus gara" dana 😭😤😡, abis tf nom gede ke bank seller, udah masukin bank tujuan + no nya bener, an nya juga udh bener, tulisan tf nya berhasil, tapi seller bilang belom masuk, dia ss rek nya jga uang nya bneran belum masuk, gue udh mau jantungan di situ, ngechat cs dana, tanya ke ai, si seller juga ngehubungin cs bank nya, ampe riweuh, eh tiba" u…
🌳 bagus nya jual di berapa ya, akun prib dari 0, ada sisa dm 1K+ an, wdp on 50 harian, spin kagura legend tinggal lanjutin aja udah 170crest, all match masih under 1K wr 60% an
🌳 bizz ini aku kan beli apk prem ya di rc sellernya, nah aku udah kirim ss login ke dia, ternyata dia punya ch khusus gitu buat send proof login sama rnk, terus aku stalk lah chnya sampe ke bot auto ordernya dan ada ternyata ch khususnya jadi aku kirim juga disitu, jadinya 2 kali, nah tp aku lupa scroll ternyata dibawahnya ada rnk, aku ga isi 1x24 jam. beberapa hari kemudian aku order lagi baru tuh dia suruh send ss …
🌳 angela cc & flo cc 300an dapat ga kirakira bizz??
🌳 hai bole tau nda kisaran harga full floryn yg ga sampe terhormat
🌳 gimana cara nya supaya ga badmood balesin chat buyer yg dry text ya? aku tipikal mirror typing, kalo buyernya dry text, aku bakal badmood dan bales dry text jg🥲🥲🥲
🌳 ada yang tau bot ce kgm kahh?
🌳 biz, bisa kah send robux via donate buyer? Soalnya dia limit menerima robux
🌳 bizz jasa yang beliin hero yang send by request itu apaa si😭 aku cari cari dibase wtb ngomong kaya gini pada kurangg ngertii, aku juga bingungg
Showing the 12 most recent of 1,389 posts we hold for @Bizfess. 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
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.
Mentions
Named by 5 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.
Names
Channels on the register whose handles appear in this channel's posts.
@jemarist · 17,4952 posts♡ Crème & Crumbs.°. ݁₊ 🥨
@bakerycrumbs · 6,7241 postCreme & Crumbs Catalog
@CremeCrumbsCatalog · 341 post@Kamiss x @DasarT_T | OPEN
@Kamiss · 2,6131 postPanduan ZonaWTB!
@PanduanZonaWTB · 201 postAVAIL REKBER
@rekberfamous · 25,3901 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Bizfess named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 2 September 2026 – 2 September 2026
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 November 2026 — this entry's latest reading, not the date you are reading this.
“BIZFESS 🌳” (@Bizfess), 17,629 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/Bizfess.
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.