Telegram RegisterThe public register of Telegram
Telegram profile photo for KYC WTB | WTS Ezmart

Channel

KYC WTB | WTS Ezmart

@ezmartKYC

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

5subscribers

+1 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-1002763993246
TypeChannel
Username@ezmartKYC
Created4 June 2025 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live10 October 2026
Measurements held5
Confirmed unchanged2 times, most recently 10 October 2026
On Telegramt.me/ezmartKYC

Topic

Hacking & security — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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

4657 August 2026 — 4 subscribers13 August 2026 — 4 subscribers5 September 2026 — 5 subscribers12 September 2026 — 6 subscribers29 September 2026 — 5 subscribers7 August 202629 September 2026
5 measurements spanning 53 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4–6 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Sept 2026, 11:375-1
12 Sept 2026, 15:596+1
5 Sept 2026, 03:395+1
13 Aug 2026, 05:164no change
7 Aug 2026, 16:094first reading

Engagement

10 posts held, back to 4 June 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 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 10 posts for this entry, the most recent from 22 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
14s
Average length
7s

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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 10 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 10 most recent posts we hold, published 4 June 2025 to 22 June 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.

Recent posts

22 Jun 2025, 12:51 UTC37 viewsread 13 August 2026

WTB - $400 #WTB Business Registration ID picture Selfie Video Easy Money 💸🤑 @retr0_17

14 Jun 2025, 00:46 UTC46 viewsread 13 August 2026

Учетные записи белого списка Stripe уже доступны Проверено KYC — уже 1–2 транзакции. Мы можем создать вашу электронную почту, веб-сайт и банк, чтобы вы не могли изменить черный список Stripe. ✅Повторная доставка и замена, если есть какие-либо проблемы! 👉🏻[這裡聯系我們 Chat with us @retro_17

7 Jun 2025, 21:22 UTC61 viewsread 13 August 2026

Stripe Whitelist Accounts NOW AVAILABLE KYC Verified - 1-2 Transactions already. We can create with your email, website, and bank, to prevent Stripe blacklist from you changing it. Reship & replacement if there are any problems! Stripe 账户现已开放 KYC 已验证 - 已完成 1-2 笔交易。 我们可以根据您的邮箱、网站和银行账户创建账户,以防止您更改 Stripe 黑名单。 ✅ 如有任何问题,可重新发货或更换!

7 Jun 2025, 11:52 UTC69 viewsread 13 August 2026

🧨欧洲地区Stripe 经理白名单号(个人账号且已经验证人脸)接受少量预定 🙅‍♂️要求:需要自己提供干净 的欧洲银行 和注册的域名 网站 邮箱 Stripe manager whitelist accounts in Europe are accepting little of reservations(personal account and already verified face) 🙅‍♂️Requirements: You need to provide a clean European bank and registered domain name website email 价格偏贵 且稀少 拒付率需要保持在12%以内!!! ✅如果我没回复您的消息请隔天再给我发消息 消息太多了! ✅If I don't reply to your message please message me the next day T…

6 Jun 2025, 17:22 UTC34 viewsread 13 August 2026
Photo

WTS | KYC Stripe Accounts - We use your email, bank, and website so you have full access at all times. - We verify it - Reship/Reverify for any issues with accounts We are also working on other KYC. Need an account verifying, reach out! @retr0_17

6 Jun 2025, 17:20 UTC18 viewsread 13 August 2026
Photo

WTS | KYC Stripe Accounts - We use your email, bank, and website so you have full access at all times. - We verify it - Reship/Reverify for any issues with accounts We are also working on other KYC. Need an account verifying, reach out! @retr0_17

4 Jun 2025, 23:11 UTC30 views1 reactionsread 13 August 2026
Photo

WTS | KYC & Stripe Accounts - We use your email, bank, and website so you have full access. - We verify it - Reship/Reverify for any issues with accounts We are also working on other accounts. Need an account verifying, reach out! @retr0_17

❤1

4 Jun 2025, 22:51 UTC51 viewsread 13 August 2026

WTB | Latvia Business Registration Must have Latvia Smart ID. We will complete the forms and make the required payment. Open to offers WTB | Latvijas uzņēmumu reģistrācija Jābūt Latvijas Smart ID. Mēs aizpildīsim veidlapas un veiksim nepieciešamo maksājumu. Atvērts piedāvājumiem @retr0_17

Showing the 10 most recent of 10 posts we hold for @ezmartKYC. 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.

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 29 September 2026 — this entry's latest reading, not the date you are reading this.

“KYC WTB | WTS Ezmart” (@ezmartKYC), 5 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/ezmartKYC.

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.