Telegram RegisterThe public register of Telegram
Telegram profile photo for Bibot.Trade - Free Binance Trading Bot

Channel

Bibot.Trade - Free Binance Trading Bot

@binance_bot_free

On this record: Growth · Engagement · Posts · Citations · Cite this entry

226subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001272024203
TypeChannel
Username@binance_bot_free
CreatedBetween 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live20 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 20 August 2026
On Telegramt.me/binance_bot_free

Growth

2262302286 August 2026 — 229 subscribers7 August 2026 — 229 subscribers7 August 2026 — 230 subscribers20 August 2026 — 226 subscribers6 August 202620 August 2026
4 measurements spanning 14 days, net -3. 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 225–231 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 09:42226-4
7 Aug 2026, 04:57230+1
7 Aug 2026, 02:48229no change
6 Aug 2026, 05:33229first reading

Engagement

18 posts held, back to 1 September 2024the 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 18 posts for this entry, the most recent from 1 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

1 Mar 2026, 09:32 UTC272 viewsread 7 August 2026
Photo

The result of the month is -6.9% on Spot and +1.8 on Futures.

8 Jan 2026, 12:47 UTC370 viewsread 7 August 2026
Photo

We finished last month (December) with about zero results. Over the past year, the result is -40% on Spot and -30% on Futures.

1 Dec 2025, 08:38 UTC398 viewsread 7 August 2026
Photo

Last month result is 9.2% loss on Spot and 3.7 on Futures.

1 Nov 2025, 04:26 UTC360 viewsread 7 August 2026
Photo

Last month there was a large flash crash in the market and the bot lost about 25% of the deposit.

1 Oct 2025, 11:18 UTC341 viewsread 7 August 2026
Photo

We finished a month with the result of +2.5% of the profit on Spot and +0.9% on Futures.

1 Sept 2025, 06:21 UTC321 viewsread 7 August 2026
Photo

Good month! Finished with a profit +5.7% on Spot and +11.7% on Futures.

1 Aug 2025, 11:06 UTC345 viewsread 7 August 2026
Photo

We finished this month with a result of +5.4% of the profit on Spot and +1.9% on Futures.

1 Jul 2025, 07:10 UTC363 viewsread 7 August 2026
Photo

The month was finished with near zero result: -1.6% of the loss on Spot and +0.4% on Futures.

1 Jun 2025, 06:44 UTC360 viewsread 7 August 2026
Photo

The month ended with +2.5 profit on SPOT and +9% on FUTURES.

2 Mar 2025, 15:46 UTC621 viewsread 7 August 2026
Photo

Almost nothing has changed since last month. No change in the bot profit.

3 Feb 2025, 14:09 UTC609 viewsread 7 August 2026
Photo

The year started off very badly. The bot lost about 40% of its deposit due to the market crash.

2 Jan 2025, 08:55 UTC614 viewsread 7 August 2026
Photo

Finished this month with a loss of -9.9% on Spot and -3.6 on Futures. Because of this fall, the year ended somewhat worse than expected, with a total of about +35% profit to deposit.

Showing the 12 most recent of 18 posts we hold for @binance_bot_free. 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.

Citation-graph rank

Citation-graph rank — 588,288 of 1,605,487entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“Bibot.Trade - Free Binance Trading Bot” (@binance_bot_free), 226 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/binance_bot_free.

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.