Telegram RegisterThe public register of Telegram
Telegram profile photo for liquidityladder

Channel

liquidityladder

@liquidityladderbnbbase

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

457subscribers

+232 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-1003488519572
TypeChannel
Username@liquidityladderbnbbase
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 12 September 2026
On Telegramt.me/liquidityladderbnbbase

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

2254573416 August 2026 — 225 subscribers7 August 2026 — 225 subscribers7 August 2026 — 226 subscribers15 August 2026 — 252 subscribers21 August 2026 — 274 subscribers28 August 2026 — 287 subscribers4 September 2026 — 358 subscribers12 September 2026 — 457 subscribers6 August 202612 September 2026
8 measurements spanning 37 days, net +232. 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 190–492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Sept 2026, 17:21457+99
4 Sept 2026, 17:20358+71
28 Aug 2026, 22:25287+13
21 Aug 2026, 14:15274+22
15 Aug 2026, 00:57252+26
7 Aug 2026, 05:20226+1
7 Aug 2026, 03:02225no change
6 Aug 2026, 22:03225first reading

Engagement

19 posts held, back to 24 July 2026the 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 19 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

41 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 48.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2048.8%
👍1434.1%
😢37.32%
👌24.88%
🔥24.88%

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 6 of the 19 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 41 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 24 July 2026 to 5 August 2026, 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

5 Aug 2026, 10:46 UTC131 viewsread 7 August 2026

через неделю, мб 2 думаю будет повышение цен, для старых кто продляет - сохраняются, для новых цена будет 100/мес

4 Aug 2026, 07:52 UTC133 views1 reactionsread 7 August 2026

Популярные ошибки и что делать за неделю на 6к открытых позиций: execution reverted: TRANSFER_FROM_FAILED — 237 раз. Зачастую такая ошибка возникает если цена уже провалилась в диапазон, который ещё не открыт. Такая поза уже требует токен, которого нет. Что бы меньше такого ловить нужно либо ставить диапазон не от 0 а от -1 или использовать Market APE в настройках. Сюда же ошибка типа - positions overlap current po

1

3 Aug 2026, 16:08 UTC133 viewsread 7 August 2026

Если кто то сегодня оплачивал в боте подписку и вам не пришёл код, напишите - @jolykedr и добавил кодов, не думал что там быстро закончатся и кто в целом оплачивал за последнюю неделю, то не забудьте активировать - @Pools_BSC_BASE_bot + настриоть под себя, если кого пропустил и не одобрил, так же пишите

3 Aug 2026, 15:45 UTC130 viewsread 7 August 2026

сейчас буду грузить обнову, серв упадёт на секунд 15-30, прожимайте ф5 если выдаст ошибку по типу api error 501

3 Aug 2026, 11:04 UTC133 views8 reactionsread 7 August 2026

и ещё из актуального, не заходите в токены на конце которых 88888, есть большой риск что такую позу потом не закрыть, ни в софте, ни в юнике, нигде там возможно есть способ закрыть позы которые не содержат щитка, но если в них уже есть накопленные комиссии - тоже не даст. В теории такую позу можно закрыть если не собирать с неё комиссию, но я не проверял, не уверен

👍6👌2

3 Aug 2026, 10:59 UTC136 views16 reactionsread 7 August 2026

по поводу новых обнов, нововведений, они пока на паузе, не знаю насколько долго, уже многое сделано и хуки что бы не давать комсу юнику и новые свапалки и доп функционал и запы частично переделаны, но я пока ничего из этого не заливаю, потому что начали вылазить различные баги, починкой которых и занимаюсь в первую очередь. А времени тестировать новый функционал пока нету, поэтому обновы ждут своего часа самая непри

16

1 Aug 2026, 17:15 UTC150 viewsread 7 August 2026

проверьте коши, скинули 8ч назад

31 Jul 2026, 17:42 UTC171 views8 reactionsread 7 August 2026
Photo

старался пулить в этом месяце, и слоу, и лудку, в итоге с слоу даже меньше вышло и больше нервотрёпки, не моё это, но с такой метой сложно было не заработать. Пробовал отделить стратки на 3 разных коша, но в итоге вышла каша, 2-рой акк +- на половину из слоукуков какие у вас результаты за июль?

👍6🔥2

29 Jul 2026, 14:16 UTC201 views6 reactionsread 7 August 2026
Photo

в общем, они за такое рефанд не делают и не должны, но всё же он будет в размере 50%, попробовал договорится на большее - не вышло переведут завтра и на данный момент единственный вариант больше не попадаться на такое - не скипать превью, а смотреть на сумму свапа. Потому что со своей стороны я не могу давать собственную квоту, что бы сравнивать с их и отклонять в подобных ситуациях, в прошлый раз я сделал просто з

😢3👍21

29 Jul 2026, 09:11 UTC175 viewsread 7 August 2026

готово, система что должна была автоматом поднимать на случай аварии в итоге в бесконечный цикл вошла, хорошо что сейчас выяснилось, перепроверьте позы на всякий кто открывал что то в момент падения

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

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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.

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

“liquidityladder” (@liquidityladderbnbbase), 457 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/liquidityladderbnbbase.

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.