Channel
@QualityC0ntrol
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
128subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002066871680 |
|---|---|
| Type | Channel |
| Username | @QualityC0ntrol |
| Description | Let’s make some money 🤝 |
| Created | Between 1 November 2023 and 31 May 2024— 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/QualityC0ntrol |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 01:45 | 128 | no change |
| 7 Aug 2026, 13:04 | 128 | first reading |
20 posts held, back to 28 January 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 11 July 2025. An engagement rate over an empty window would be a number about nothing.
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. Below Telegram’s rounding threshold, so these counts are exact.
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.
4 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 100.0% |
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 2 of the 20 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 28 January 2025 to 11 July 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.
$NGA pumped up about 4x from the local bottom where I recalled it. 50k > 200k This guy https://x.com/theonlynom aped on his public wallet. Part of the bonk team… probably nothing. (Buy some $NGA)
❤3
Been a while but no way I couldn’t share this 😂
Congrats to my fellow Spyre member Sugar for winning his crypto fight night battle One punch bro was done lmao
That’s the best part about DLMMs, we play the swings either way 🤝
$HOOD will win almost 70k holders all who want it to go to 1$, we can get at least 10% there
$HOOD pool printing some nice fees in these ranges. 50/50 Ask-Bid recommended here. If you got time to watch it even Curve setup is good 🤝 https://app.meteora.ag/dlmm/6ehEi3xc5DX3SVPiBpnRwPW3nQJBTzDynA26ce3AnYPp
Opened a $PKIN ( https://app.meteora.ag/dlmm/9GLWwRU9g7qscQQp65ZBHy6syKuyaytbEbHQeh1sqZ3p) and a $LUX ( https://app.meteora.ag/dlmm/9GLWwRU9g7qscQQp65ZBHy6syKuyaytbEbHQeh1sqZ3p ) pool for today Both 50/50 ask-bid setups, let’s see how these play out 🤝
Currently in $HOOD 100 step pool, really nice so far https://app.meteora.ag/dlmm/6ehEi3xc5DX3SVPiBpnRwPW3nQJBTzDynA26ce3AnYPp
JUST IN: $106,000 Bitcoin @WatcherGuru
Hoping this is bottom for $jelly , opening a token single sided ask-bid setup here and heading out for the day 🫡 https://app.meteora.ag/dlmm/Hr3byzHKDa7U9MgnfNr9tvRxzvX7fz3sZLgfDgPHGQ15
https://app.meteora.ag/dlmm/FZEYvZyT1HenRGcWqYaGtPfMsGNJwk3F4iGzr8gMzLTR
Currently running a 50/50 Ask-Bid pool on $XYZ , doing great so far
Showing the 12 most recent of 20 posts we hold for @QualityC0ntrol. 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.
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.
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.
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.
“Quality Control” (@QualityC0ntrol), 128 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/QualityC0ntrol.
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.