dito nalang para ons lang ang dating😭

Channel
fou x bulks
@fouxbulks
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
66subscribers
-9 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 | -1003883187599 |
|---|---|
| Type | Channel |
| Username | @fouxbulks |
| Created | 13 March 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/fouxbulks |
Topic
Software piracy — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 37% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 14:58 | 66 | -3 |
| 27 Sept 2026, 17:37 | 69 | -1 |
| 15 Sept 2026, 06:57 | 70 | -1 |
| 8 Sept 2026, 08:56 | 71 | -2 |
| 29 Aug 2026, 19:16 | 73 | -1 |
| 15 Aug 2026, 01:34 | 74 | -1 |
| 9 Aug 2026, 21:31 | 75 | no change |
| 7 Aug 2026, 19:04 | 75 | first reading |
Engagement
19 posts held, back to 13 March 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 10 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
16 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5359369473096688455 | 4 | 25.0% | |
| custom 5438349364709846171 | 4 | 25.0% | |
| custom 6332211082110703407 | 4 | 25.0% | |
| custom 6332125148405045066 | 2 | 12.5% | |
| custom 6305214197588302402 | 1 | 6.25% | |
| custom 6332589700657714078 | 1 | 6.25% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 6 of the 19 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 13 March 2026 to 10 May 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
. ⭐ batch no. three ⭐ capcut 7d solo infos % :: 💙 fw target 10 | 5php 🩵 can’t tingi 🩵 provided 🩵 within a day fixing time status: open! #% lineup 0/10 ! 🤩 — paid 🤩 — not paid 💦 — processing 🤩 — dropped
wipe batch no more team heads 😞🤞🏻
regarding peeps here read announcement dito, to those ayaw magpa rf willing ba kayo tumanggap cc head na need vpn? yung dati kong supp na patch na meth nya 💔 sayang since no need vpn na yun eh and will probably price hike narin 😭💔
. ⭐ batch no. one ⭐ netflix sla fvisa infos % :: 💙 fw target 3 | 350php 🩵 fvisa 🩵 ph based 🩵 can change ur dom but nw after. 🩵 owner/admins can code status: open #% lineup 0/3 ! 🤩 — paid 🤩 — not paid 💦 — processing 🤩 — dropped
custom 53593694730966884552custom 63052141975883024021
. ⭐ batch no. three ⭐ capcut 35d head infos % :: 💙 fw target 10 | 160php 🩵 weekly rep 🩵 can’t tingi 🩵 provided 🩵 0-3 fixing time status: cancelled! #% lineup 3/10 ! justwista - 2 xoxovannesa - 1 🤩 — paid 🤩 — not paid 💦 — processing 🤩 — dropped
custom 54383493647098461714custom 53593694730966884552
fou x bulks pinned «. ⭐ batch no. two ⭐ capcut 35d head infos % :: 💙 fw target 10 | 130php 🩵 weekly rep 🩵 can’t tingi 🩵 provided 🩵 0-3 fixing time status: closed #% lineup 10/10 ! eirlyse_x - 🤩 kashmlx - 5 🤩 …»
hi tinks sa mga msgs niyo regarding capcutz
custom 63321251484050450662
Signed ᰋ. ࣪ chipi ~ offline / zzz
get nyo na, 7d capcut teams head is ₱40-₱50 kaya tas yan 35 days na worth 5x 7d capcut teams bleeee ❤️
. ⭐ batch no. two ⭐ capcut 35d head infos % :: 💙 fw target 10 | 130php 🩵 weekly rep 🩵 can’t tingi 🩵 provided 🩵 0-3 fixing time status: closed #% lineup 10/10 ! eirlyse_x - 🤩 kashmlx - 5 🤩 cybershan - 🤩 lauvelise - 🤩 tomatces - 🤩 cauffxx - 🤩 🤩 — paid 🤩 — not paid 💦 — processing 🤩 — dropped
custom 63322110821107034071custom 63325897006577140781
for rf cgpt, for capcut kinain ako katamaran mamayang hapon drop
custom 63322110821107034072
. ⭐ batch no. two ⭐ spotify 1 month famhead infos % :: 💙 fw target 10 | 150php 🩵 carded 🩵 can't tingi 🩵 provided 🩵 us based 🩵0-3 fixing time status: closed #% lineup 6/10 ! zaskiyax - 1🤩 Iovechi - 1🤩 kashmlx - 2🤩 luvdzy - 1🤩 sachikofuji - 1🤩 🤩 — paid 🤩 — not paid 💦 — processing 🤩 — dropped
custom 63322110821107034071
Showing the 12 most recent of 19 posts we hold for @fouxbulks. 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
Named by 1 registered channel — 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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“fou x bulks” (@fouxbulks), 66 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/fouxbulks.
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.