Channel
@wtpenglish
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
140subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001485658935 |
|---|---|
| Type | Channel |
| Username | @wtpenglish |
| Description | Join the chat https://t.me/wtpeng |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/wtpenglish |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 22:16 | 140 | no change |
| 6 Aug 2026, 18:55 | 140 | first reading |
16 posts held, back to 29 July 2022 — 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 16 posts for this entry, the most recent from 9 December 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 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.
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.
Wecco company invites you to undergo the verification procedure in the CryptoAccelerator project, via telegrambot: @AcceleratorAuditBot To complete the procedure, you need to go to the bot, send it your login from the project, email (specified when registering in the project) and send your own selfie with a piece of paper on which your real name, login, email and date of the selfie are written
Signed Elena Bagirova
Video, posted without a caption
Signed Elena Bagirova
Photo, posted without a caption
Signed Elena Bagirova
Wecco company invites you to undergo the verification procedure for the KGDAO project, via telegrambot: @KGDAOauditBOT To complete the procedure, you need to go to the bot, send in your login from the project, email (specified when registering in the project) and send your own selfie with a piece of paper on which your real name, login, email and date are written
Signed Elena Bagirova
Hello, everyone! We start verification in the projects of the Wecco company. First projects for verification are Webtokenprofit and WecAuto. You can verify in these bots @WECCOauditBOT @WECAUTOauditBOT These are the official bots of the company. It is in Russian but you can use a Google translator for translation from Russian into your language. In the bot you need to specify following data To complete the pro…
Signed Elena Bagirova
🗣 Dear partners! ✅ Today we are starting the preliminary testing phase of the WEC 2.0 blockchain ✅ All code for testing will be publicly available by the link: https://github.com/wec-chain/node-test ✅ The master node is already available for download - a network nodetask is to store a copy of the blockchain and sign blocks. Installation instructions here 👉 https://telegra.ph/Kak-ustanovit-testovuyu-nodu-WEC-11-03 …
Signed Elena Bagirova
🗣 Dear partners! 🔖This is a summary of the briefing: ✅ The company continues to work, optimizes costs; ✅ Websites are connected to more budget servers; ✅ The resumption of the website' operation will be phased; ✅ We continue the development of the blockchain.
Signed Elena Bagirova
🗣Dear partners! ❗️ iOS mobile device users need to install the KGWallet app on their Android mobile device. ➡️ Log in to the KGWallet app using your seed phrase and take a screenshot of the available funds on your balance; ➡️ Next, you need to contact KGWallet support to transfer your funds manually to the exchange balance. 📌 KGWallet Support Contacts: ✅ Online chat in Russian - https://direct.lc.chat/12063651/9…
Signed Elena Bagirova
🗣Dear partners! ⚠️ Token transfer maintenance from the KG-chain blockchain to the WEC 2.0 blockchain has begun. If coins are not displayed in your application, contact the KG-wallet support so that they fix how many coins you did not have time to transfer to the exchange and to which exchange account you are waiting for the transfer. Balance transfer requests will be accepted until September 15 in. The accruals…
Signed Elena Bagirova
🗣Dear community! ❌Because of mechanical reasons, KWEC, KGC, KUSD, KRA deposit and withdrawal functions via the KGChain network are temporarily disabled. ✅About the resumption of operations, we will notify additionally. We apologize for any inconvenience caused. 🤝 Best regards, Wecco company!
Signed Elena Bagirova
🗣Dear partners! ✅Now in the KGDAO project in the Settings tab, you can switch on a Telegram information bot. ✅ To do this, go to the Settings tab, click the "Enable" button (Telegram will open) and start the bot by clicking the "Start" button. 🤝 Best regards, Wecco company!
Signed Elena Bagirova
🗣Dear partners! ‼️We remind you that since September 4, 2022, the KGWallet app will switch to another network. In order to have time to withdraw your coins, do not stake KGC since August 4, 2022, otherwise, your funds will be lost PERMANENLY! ‼️Until 04.09.2022, you need to withdraw all your assets from the KGWallet application because making maintenance! ‼️All verification requests will be rejected, so do not ap…
Signed Elena Bagirova
Showing the 12 most recent of 16 posts we hold for @wtpenglish. 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.
@wtpenglish 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“WECCO English News Channel” (@wtpenglish), 140 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/wtpenglish.
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.