uber eats , bolt food , wolt -50% order - @leycontento

Channel
Taxi 🚕 | Food | -50% discount
@foodtaxidiscount
On this record: Topic · Growth · Engagement · Posts · Cite this entry
198subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001512003979 |
|---|---|
| Type | Channel |
| Username | @foodtaxidiscount |
| Created | Between 1 August 2021 and 9 December 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/foodtaxidiscount |
Topic
Ecommerce storefront — 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 24 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 16:37 | 198 | +2 |
| 10 Sept 2026, 09:59 | 196 | -1 |
| 31 Aug 2026, 12:57 | 197 | +1 |
| 23 Aug 2026, 17:37 | 196 | -2 |
| 16 Aug 2026, 15:52 | 198 | +1 |
| 7 Aug 2026, 07:32 | 197 | no change |
| 7 Aug 2026, 07:28 | 197 | first reading |
Engagement
20 posts held, back to 9 December 2021 — 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 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 20 posts for this entry, the most recent from 3 March 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Принимаю заказы на еду (-50%) Минималка - 20$ в мою сторону = 40$ корзина. 🥘🧆🍕🍟🍔 Uber eats : Spain 🇪🇸 France 🇫🇷 Netherlands 🇳🇱 USA 🇺🇸 Mexico 🇲🇽 Bolt food : - Poland 🇵🇱 - Czech Republic 🇨🇿 - Estonia 🇪🇪 - Кипр 🇨🇾 -Латвия 🇱🇻 оплата - btc, usdt(trc20) order - @leycontento
😎😎
😊
🙊
👌
Запускаем Uber eats (-50%) в USA 🇺🇸 Минималка - 20$ в мою сторону = 40$ корзина. оплата - btc, usdt(trc20) order - @leycontento
Принимаю заказы на еду (-50%). Минималка - 20$ в мою сторону = 40$ корзина. оплата - btc, usdt(trc20) order - @leycontento
market 😍
Принимаю заказы на еду (-50%). Минималка - 20$ в мою сторону = 40$ корзина. оплата - btc, usdt(trc20) , paysend order - @leycontento
🙊
👍
Showing the 12 most recent of 20 posts we hold for @foodtaxidiscount. 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Taxi 🚕 | Food | -50% discount” (@foodtaxidiscount), 198 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/foodtaxidiscount.
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.