Adquirir Kurumi nunca habΓa sido tan fΓ‘cil. ConviΓ©rtete en un experto carder con nuestra asesorΓa y acceso al exclusivo grupo de usuarios Kurumi Premium, donde podrΓ‘s recibir apoyo, hacer preguntas y obtener ayuda adicional. β¦ Disponemos de una amplia lista de comandos para facilitarte la obtenciΓ³n de lives. Nuestro soporte es eficiente, con actualizaciones constantes y mantenimiento discreto. Β‘OlvΓdate de proxies cβ¦

Channel
πππ‘π¦ πππ¬ β
@BinsDayOficial
On this record: Topic Β· Growth Β· Engagement Β· Posts Β· Citations Β· Handles named that no longer answer Β· Cite this entry
21,852subscribers
-739 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 10,000β31,623.
Register entry
| Telegram ID | -1001491056053 |
|---|---|
| Type | Channel |
| Username | @BinsDayOficial |
| Created | Between 1 April 2019 and 30 September 2021 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/BinsDayOficial |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 22:01 | 21,852 | -106 |
| 7 Sept 2026, 19:59 | 21,958 | -96 |
| 4 Sept 2026, 22:19 | 22,054 | -47 |
| 3 Sept 2026, 05:52 | 22,101 | -54 |
| 2 Sept 2026, 02:33 | 22,155 | -45 |
| 1 Sept 2026, 02:14 | 22,200 | -30 |
| 31 Aug 2026, 02:12 | 22,230 | -29 |
| 30 Aug 2026, 01:26 | 22,259 | -32 |
| 28 Aug 2026, 22:25 | 22,291 | -20 |
| 27 Aug 2026, 21:52 | 22,311 | -13 |
| 27 Aug 2026, 00:43 | 22,324 | -15 |
| 25 Aug 2026, 22:32 | 22,339 | -10 |
| 24 Aug 2026, 20:03 | 22,349 | -29 |
| 23 Aug 2026, 02:24 | 22,378 | -13 |
| 21 Aug 2026, 13:26 | 22,391 | -12 |
| 20 Aug 2026, 15:27 | 22,403 | -8 |
| 19 Aug 2026, 17:56 | 22,411 | -14 |
| 18 Aug 2026, 16:17 | 22,425 | +1 |
| 17 Aug 2026, 18:06 | 22,424 | -15 |
| 16 Aug 2026, 14:04 | 22,439 | first reading |
Engagement
15 posts held, back to 3 August 2023 β the reader has reached the start of this channelβs public history, so this is the full archive Telegram still exposes. Read across 58 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 15 posts for this entry, the most recent from 19 August 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Muchas gracias @Kevin22012
π ONLYFANS 50$ π - al primero en decirme cuΓ‘nto es 5+5 gana By: @Kevin22012 Escribir a : @CAPTURASBINSBOT
Sticker, posted without a caption
Photo, posted without a caption
Gracias
Thank you
thx bro
[email protected] $50 Germany678 Onlyfans Ss in the chat
Gracias
Sticker, posted without a caption
Gracias @Kevin22012
Showing the 12 most recent of 15 posts we hold for @BinsDayOficial. 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.
Forward network
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channelβs posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@BinsDayOficial named 2 handles 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.
Never seen alive
References a handle that is not a live channel β we have no record it ever was one.
named in 26 posts, 8 August 2026 β 16 August 2026
named in 14 posts, 8 August 2026 β 16 August 2026
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 10 September 2026 β this entry's latest reading, not the date you are reading this.
βπππ‘π¦ πππ¬ β β (@BinsDayOficial), 21,852 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/BinsDayOficial.
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.