Technology — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 the other topics.
Growth
15 measurements spanning 99 days, net +58. 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 656–737 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Nov 2026, 18:08
724
+1
6 Nov 2026, 06:17
723
-5
29 Oct 2026, 09:06
728
+2
21 Oct 2026, 08:46
726
+4
14 Oct 2026, 06:47
722
+2
7 Oct 2026, 07:55
720
+15
26 Sept 2026, 18:55
705
+6
13 Sept 2026, 04:01
699
+1
5 Sept 2026, 07:55
698
+11
28 Aug 2026, 15:42
687
+13
20 Aug 2026, 23:18
674
+2
15 Aug 2026, 00:08
672
+7
8 Aug 2026, 06:41
665
-1
7 Aug 2026, 07:31
666
no change
7 Aug 2026, 07:29
666
first reading
Engagement
20 posts held, back to 16 August 2025 — 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 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
224 reactions across 19 posts, in 18 distinct kinds. The most used accounts for 32.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
72
32.1%
👍
56
25.0%
🔥
43
19.2%
👌
9
4.02%
👏
8
3.57%
😢
6
2.68%
🏆
4
1.79%
😁
4
1.79%
🤨
4
1.79%
🤬
4
1.79%
😍
3
1.34%
🥴
3
1.34%
🥰
2
0.893%
🥱
2
0.893%
⚡
1
0.446%
🎉
1
0.446%
🤔
1
0.446%
🤯
1
0.446%
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 19 of the 20 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 224 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 16 August 2025 to 1 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.
Telegram Stars
Stars received
3
across the posts below
Posts paid on
3
of 19 we hold a reading for · 16%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ig_api. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 16 August 2025 to 1 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🔧 Technical work
Currently, technical work is being carried out on the servers to improve the stability and quality of the API.
During the work, the following is performed:
⚡️ optimization of request processing;
🚀 improvement of the server infrastructure performance;
📈 improvement of the API response speed;
🛡 strengthening the stability and fault tolerance of the services.
During the work, there may be short-te…
✅ Location endpoints have been restored
Lookup for locations has been fixed, and it now responds stably:
• /location_search/?name= — search for locations by name
• /locations/?location_id= — media by location id
✅ We have added our own proxy servers to the rotation.
The new proxies are already being used in production and are showing excellent response rates during testing. This helps improve request stability, reduce errors, and increase the overall reliability of data collection.
We will continue monitoring performance and gradually expand the proxy pool to maintain the best possible results for our users.
Thank you for…
⚠️ Dear users!
We are currently experiencing temporary issues with Instagram API requests.
This may cause some features to become unstable or experience delays. We are currently working to resolve the issue and are doing everything possible to restore stable service as soon as possible.
Thank you for your understanding and patience ❤️
⚠️ Note: when requesting the next page, you must include the acc_id parameter obtained from the first response.
"pagination":{"id_acc":1648512}
The same approach is used for hashtag pagination as well.
📷 Reels Pagination: What Changed (beta)
Previously, next pages could be loaded using a different account, while max_id is tied to a session — this often caused the error “The service was not able to process your request.”
Now the entire pagination chain is bound to a single account. The response includes pagination.id_acc, which must be sent along with max_id for the next page.
If the account becomes unavailable (…
We carried out technical work on the API: we fixed errors that could cause individual requests to fail in a number of scenarios.
We have implemented a fix and stabilized data processing. Everything is working normally now.
❤️ Dear FlashAPI Users,
We are currently working on improving the quality of our proxy network and enhancing overall API response performance.
During this period, you may experience short-term interruptions or brief instability in service. Please rest assured that these updates are aimed at delivering a faster, more stable, and more reliable experience for all users.
We appreciate your patience and understanding.
…
🚀 FLASHAPI Promo! 🚀
Use the promo code 7V4XEP and get 20% OFF 🔥
💰 Discount: 20% OFF
💳 Promo code: 7V4XEP
⏳ Valid until: January 25, 2026
Don’t miss your chance to save — activate the promo code now!
👉 https://flashapi.ru
🚀 New Feature: Telegram Notifications
Stay on top of your API usage with real-time Telegram notifications!
📱 What's New:
• Get instant alerts when your balance drops below your threshold
• Receive warnings when your request quota is running low
• Never miss important updates about your account
⚙️ How It Works:
1. Connect your Telegram account in Settings → Notifications
2. Set your custom thresholds for balance an…
🔔 API Update
The Search Hashtag endpoint now supports a new parameter: tabs.
This parameter allows you to select the content type:
top — top posts
recent — recent posts
clips — clips/reels
The parameter is optional and is passed as the second argument after hashtag.
https://flashapi.ru
👍5👏3❤2🤨1
Signed API PROFI
Showing the 12 most recent of 20 posts we hold for @ig_api. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 14 November 2026 — this
entry's latest reading, not the date you are reading this.
“Instagram Scraper 2022” (@ig_api), 724 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/ig_api.
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.