Channel
@qqfk69
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
17subscribers
-1 since we began measuring on 11 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001663902573 |
|---|---|
| Type | Channel |
| Username | @qqfk69 |
| Created | 15 February 2023 — measured — dated from the channel’s first post |
| First recorded | 13 September 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/qqfk69 |
Marketing & affiliate — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 16 October 2026 and assigned it the closest of 31 fixed categories, at 46% 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 |
|---|---|---|
| 14 Oct 2026, 23:55 | 17 | -1 |
| 13 Sept 2026, 12:23 | 18 | no change |
| 11 Sept 2026, 23:18 | 18 | first reading |
2 posts held, back to 15 February 2023 — 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 2 posts for this entry, the most recent from 27 February 2023. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1 | 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 1 of the 2 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 15 February 2023 to 27 February 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🇺🇸69PAY-全球支付·专注美国公户通道🇺🇸 💸代收优势💸 美国本地公户收款： 👉美国本土公户收款，收款速度快 👉国内ACH转账需要1-2工作日 👉国内FEDWIRE转账需要0-1工作日 👉国际SWIFT转账需要0-3工作日 💵代付优势💵 👉代付欧美100+国家，USDT代付 👉代付：24小时出款 👉代付到账时间：5分钟-24小时内 👉支持货币到账：本地货币 📣📣🗽欧美通道规则🗽📣📣： 1️⃣7*24代收，多条通道备用 D0实时结算 2️⃣24*7API三方代付 3️⃣转账必须填写：公司名称+卡号 4️⃣入金带金额：姓名，水单，转账方式，ID，护照 5️⃣公户收款实时入账 6️⃣入账时间：24小时 💝关于我们的服务💝 🚀我们是7*24全天候服务，您有任何问题，我们都将在线等待 🚀10秒内回复您的消息，让您在最短的时间内得到帮助；5分钟内解决问题，为您节省宝贵的时间。 💻我们的在线客服将全心全意为您提供服务，…
👍1
Channel created
Showing the 2 most recent of 2 posts we hold for @qqfk69. 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.
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.
@qqfk69 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.
References a handle that is not a live channel — we have no record it ever was one.
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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“【69PAY】专注美国支付收款通道·唯一官方频道” (@qqfk69), 17 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/qqfk69.
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.