Channel
@weliya_bet
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
7,598subscribers
-183 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001255348496 |
|---|---|
| Type | Channel |
| Username | @weliya_bet |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/weliya_bet |
Gambling & betting — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 18 Sept 2026, 13:19 | 7,598 | -14 |
| 14 Sept 2026, 11:17 | 7,612 | -8 |
| 10 Sept 2026, 17:15 | 7,620 | -24 |
| 5 Sept 2026, 04:00 | 7,644 | -20 |
| 1 Sept 2026, 15:45 | 7,664 | -15 |
| 29 Aug 2026, 17:12 | 7,679 | -20 |
| 26 Aug 2026, 11:16 | 7,699 | -12 |
| 23 Aug 2026, 14:48 | 7,711 | -12 |
| 20 Aug 2026, 07:38 | 7,723 | -22 |
| 16 Aug 2026, 21:25 | 7,745 | -23 |
| 13 Aug 2026, 03:34 | 7,768 | -12 |
| 10 Aug 2026, 08:00 | 7,780 | -1 |
| 9 Aug 2026, 23:46 | 7,781 | first reading |
14 posts held, back to 1 March 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 10 pages 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 14 posts for this entry, the most recent from 24 August 2023. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 18 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 5 months. If they remain inactive for the next 30 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
የጨዋታ ውጤት በ ቢ ሶከር Match Results by BeSoccer⚽️ 🏆ተመልካች ብቻ አይሁኑ! ማሸነፍ ይጀምሩ!⚽ @Ethio1X @Ethio1X @Ethio1X
የትላንት Draw ትኬት ትኬትይኸዉ👆👆 በሚገባ አሸንፈናል ከኛጋ የመደቡ ትርፋማ ሆነዋል እርሶስ ምን ይጠብቃሉ? FIXED ትኬቶችን በመግዛት እንዲሁም VIP በመመዝገብ አብረዉን ትርፋማ ይሁኑ💰💰💰 @Ethio1X @Ethio1X @Ethio1X
Video, posted without a caption
Video, posted without a caption
የዛሬ ጨዋታዋች እየተሸጡ ነዉ። 4 ጨዋታ 293+ODD ጨዋታውን ለማግኘት በ 👉@Ethio1X በኩል ያናግሩን 👎 0995016073 Sharp 1:00pm ሽያጭ ይዘጋል! ⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰⏰ @Ethio1X @Ethio1X
Video, posted without a caption
ለበለጠ መረጃ 📱📱📱 0995016073 @Ethio1X @Ethio1X
⚠️የአብዛኞቻቹ የጋራ ጥያቄዎች ስለሆኑ የግድ ይነበብ!!⚠️ 1.ጨዋታዎቹ ባይሳኩስ? (ጨወታዎቹ በከፍተኛ ጥንቃቄ ፊክስ ስለሚደረጉ ያለመሳካት እድላቸው 0 ነው። ግን በድንገት ባይሳካ በቀጣዩ ቀን ያለው ፊክስድ ቲፕ በነጻ ይፈጸማል 2.ለምንድን ነው ጨዋታውን ምሸጡት? (ምክንያቱም አኛም በውድ ዋጋ ገዝተን ስለምናመጣው ቢያንስ የተወሰነውን ወጪ በሽያጭ ለመሸፈንነው) 3.ምን ያክል ኦድ ነው ምሰጡት? (ሁሌም የምንሰጠው ኦድ ከ 100+በላይ ሲሆን ጨዋታዋቹ 4 ናቸው) 4.ፊክስድ ማች ምንድንነው? (በሁለቱም ቡድን በኩል ያሉ ተጫዋቾች አሰልጣኞች እንዲሁም የጨዋታ ዳኞች ከትላልቅ አቆዋማሪ ደርጅቶች ጋር አብሮ በመስራት የጨዋታውን ውጤት አስቀድሞ በመወሰን ከፍተኛ …
የጨዋታ ውጤት በ ቢ ሶከር Match Results by BeSoccer⚽️ 🏆ተመልካች ብቻ አይሁኑ! ማሸነፍ ይጀምሩ!⚽ @Ethio1X @Ethio1X @Ethio1X
የትላንት Draw ትኬት ትኬትይኸዉ👆👆 በሚገባ አሸንፈናል ከኛጋ የመደቡ ትርፋማ ሆነዋል እርሶስ ምን ይጠብቃሉ? FIXED ትኬቶችን በመግዛት እንዲሁም VIP በመመዝገብ አብረዉን ትርፋማ ይሁኑ💰💰💰 @Ethio1X @Ethio1X @Ethio1X
Showing the 12 most recent of 14 posts we hold for @weliya_bet. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“1X Bet Ethio Fixed” (@weliya_bet), 7,598 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/weliya_bet.
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.