Telegram RegisterThe public register of Telegram
Telegram profile photo for π™Žπ˜Όπ™‚π˜Όπ™ π˜Όπ™‹π™„π™Ž πŸ”₯

Channel

π™Žπ˜Όπ™‚π˜Όπ™ π˜Όπ™‹π™„π™Ž πŸ”₯

@SagarApis

On this record: Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Polls Β· Citations Β· Cite this entry

391subscribers

+0 since we began measuring on 8 November 2026

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

Register entry

Telegram ID-1004494443074
TypeChannel
Username@SagarApis
DescriptionπŸš€ SAGAR API HUB ⚑ Free Fire APIs & Tools πŸ”§ API Updates & Fixes πŸ“‘ API Status & Releases πŸ“š Docs & Usage Info πŸ‘‘ Owner: @RealSagarFF
First recorded8 November 2026
Last confirmed live8 November 2026
Measurements held2
On Telegramt.me/SagarApis

Growth

3918 Nov 2026, 17:48 β€” 391 subscribers8 Nov 2026, 18:22 β€” 391 subscribers8 Nov 2026, 17:488 Nov 2026, 18:22
2 measurements taken within a single day. 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 390–392 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Nov 2026, 18:22391no change
8 Nov 2026, 17:48391first reading

Engagement

18 posts held, back to 6 October 2026 β€” 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.

ERR Β· 30 days
69.3%
avg views Γ· 391 subscribers
Avg views / post
271
13 posts measured
Reaction rate
0.198%
reactions Γ· views Β· ER floor
Posts in window
13
of 18 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) Γ· views β€” note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days Β· latest post in window 7 November 2026
Posts held18 (6 October 2026 – 7 November 2026)
Views total3,522
Reactions total1
Forwards / commentsnot exposed by the public surface β€” not measured, not estimated
Readings taken8 Nov 2026, 18:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than β€œcorrecting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form β€” 8.12K, 3.7M β€” so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded β€” read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
4
Links
19

Lifetime counters from Telegram’s own channel header, read 8 November 2026 β€” not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❀1100.0%

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 2 of the 18 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 1 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 6 October 2026 to 7 November 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

Telegram’s own β€˜edited’ marker: 2 of 13 posts held from the last 30 days (15.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before β€” this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

7 Nov 2026, 03:56 UTC330 viewsread 8 November 2026

🚨πŸ”₯ FREE FIRE CRAFTLAND CREATOR INFO API LEAKED! πŸ”₯ πŸ“’ As per community voting, the wait is finally over! 😈 ✨ FEATURES: βœ… Get Creator Info by UID βœ… Full Creator Details βœ… All Maps Information πŸ“₯ GET ACCESS HERE πŸ‘‡ https://t.me/sagarfile_bot?start=usk9H6ye πŸ‘‘ CREDIT: @RealSagarFF πŸš€ Grab it now and explore Craftland Creator Data! πŸ”₯

4 Nov 2026, 09:03 UTC456 viewsread 8 November 2026
Poll

NEXT KOUN SA API LEAK KARU ? πŸ’€

  1. EAT TOKEN --> ACCESS+JWT TOKEN28%
  2. CRAFTLAND CREATOR INFO34%
  3. OUTFIT API31%
  4. LEVEL CHECK API31%

The shares total 124%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

2 Nov 2026, 14:15 UTC223 views0 reactionsread 8 November 2026

FREE FIRE UPGRADED GUILD INFO API πŸ”₯ ✨API ENDPOINT - https://sagar-guild-info.vercel.app/clan_info?clan_id={clan_id}&region={region} πŸ’₯ API USE - https://sagar-guild-info.vercel.app/clan_info?clan_id=3045676388&region=ind 🎊 RESPONSE - { "success": true, "credit": "Made by - SAGAR FF ⚑ | TG - @RealSagarFF", "region": "ind", "guild": { "guild_id": 3045676388, "guild_name": "SAHILγ…€LIVEβΈ™", "creation_t…

31 Oct 2026, 09:48 UTC870 viewsread 8 November 2026

πŸš€ ULTIMATE FREE FIRE GUILD INFO API IS HERE! πŸ”₯ Want to explore complete Free Fire Guild information? πŸ‘€ πŸ“Š API FEATURES: 🏰 Full Guild Information πŸ‘‘ Guild Leader Details πŸ›‘οΈ Acting Leader Information ⭐ All Officers Information πŸ“‹ More Guild Details! 🎁 GET ACCESS NOW: πŸ‘‡ Click below to get the API! πŸ“₯ https://t.me/sagarfile_bot?start=ZdfTZ3v- πŸ‘¨β€πŸ’» CREDIT: @RealSagarFF POWERED BY SAGAR FF ⚑

20 Oct 2026, 05:55 UTC390 viewsread 8 November 2026
Photo

FREE FIRE PREMIUM GUILD INFO API DONE βœ… πŸ”₯ GUILD FULL INFO πŸŽ‰ LEADER,ACTING LEADER INFO πŸ’– OFFICERS INFO ⚑ETC. API DU ISKA ? 😊

18 Oct 2026, 00:31 UTC281 views1 reactionsread 8 November 2026

πŸ›‘οΈ FREE FIRE CLAN INFO API πŸ”₯ ✨ API ENDPOINT - https://sagar-clan-api.onrender.com/info?clan_id={clan_id}&region={region} πŸ’₯ API USE - https://sagar-clan-api.onrender.com/info?clan_id=3039732394&region=IND 🎊 RESPONSE - { "Api Owner": "@sagar_akatsuki_leader", "TG CHHANEL": "@sagarofficialch", "clan_id": 3039732394, "clan_name": "HIDDENγ…€LIFE!", "created_at": "2025-03-03 11:30:22", "last_active": "2025-03-03 11:32:25"…

❀1

17 Oct 2026, 00:34 UTC191 viewsread 8 November 2026

🌍 FREE FIRE REGION INFO API πŸ”₯ ✨ API ENDPOINT - https://sagar-info-api.vercel.app/region?uid={uid}&key={key} πŸ’₯ API USE - https://sagar-info-api.vercel.app/region?uid=1205209325&key=SAGAR-FF 🎊 RESPONSE - { "owner": { "telegram": "@RealSagarFF", "credit": "Made with ❀️ by SAGAR FF" }, "accountid": 1205209325, "nickname": "EMPγ…€οΌ’οΌ―οΌ³οΌ³γ…€!!!", "region": "IND", "level": 72, "liked": 66257 } CREDIT:- @RealSagarFF OFFICIAL CHA…

16 Oct 2026, 00:30 UTC144 viewsread 8 November 2026

🚫 FREE FIRE BAN CHECK API πŸ”₯ ✨ API ENDPOINT - https://sagar-bancheck.vercel.app/bancheck?uid={uid} πŸ’₯ API USE - https://sagar-bancheck.vercel.app/bancheck?uid=18227371626 🎊 RESPONSE - { "data": { "ban_period": "1 months", "ban_status": "BANNED", "level": 2, "likes": 0, "nickname": "SAGAR31432", "region": "IND", "uid": "18227371626" }, "made_by": "SAGAR FF ⚑", "success": true, "telegram": "@RealSagarFF" } CREDIT:- @…

15 Oct 2026, 00:33 UTC119 viewsread 8 November 2026

πŸ”₯ FREE FIRE OUTFIT IMAGE API πŸ”₯ ✨ API ENDPOINT - https://sagar-outfit.vercel.app/outfit-image?uid={uid}&key={key} πŸ’₯ API USE - https://sagar-outfit.vercel.app/outfit-image?uid=1205209325&key=SAGAR 🎊 RESPONSE - πŸ–ΌοΈ Outfit Image CREDIT:- @RealSagarFF OFFICIAL CHANNEL:- @Sagarofficialch APIS CHANNEL:- @SagarApis

14 Oct 2026, 00:30 UTC124 viewsread 8 November 2026

IP INFO API πŸ”₯ ✨ API ENDPOINTS - πŸ”Ή IP INFO API - https://sagar-ip-info.vercel.app/api/v1/ip πŸ”Ή MY IP INFO API - https://sagar-ip-info.vercel.app/api/v1/myip πŸ”Ή BULK IP INFO API - https://sagar-ip-info.vercel.app/api/v1/bulk πŸ”Ή IP VALIDATE API - https://sagar-ip-info.vercel.app/api/v1/validate πŸ”Ή API STATS - https://sagar-ip-info.vercel.app/api/v1/stats πŸ”Ή API HEALTH CHECK - https://sagar-ip-info.vercel.app/api/v1/he…

13 Oct 2026, 00:31 UTC119 viewsread 8 November 2026

PINCODE INFO API ⚑ ✨ API ENDPOINT - https://sagar-pincode-info.vercel.app/api/pincode/{pincode} πŸ’₯ API USE - https://sagar-pincode-info.vercel.app/api/pincode/122052 🎊 RESPONSE - { "pincode": "122052", "postOffice": [ { "Block": "Manesar", "BranchType": "Sub Post Office", "Circle": "Haryana", "Country": "India", "DeliveryStatus": "Delivery", "Description": null, "Di…

12 Oct 2026, 00:30 UTC137 viewsread 8 November 2026

GMAIL INFO API πŸŽ‰ ✨ API ENDPOINT - https://sagar-mail-info.vercel.app/info?mail={mail} πŸ’₯ API USE - https://sagar-mail-info.vercel.app/[email protected] 🎊 RESPONSE - { "Breaches Found": [ "Error fetching data" ], "Creation Date": "2000-07-03 12:13:41+00:00", "Disposable": "No", "Domain": "garena.com", "Domain IP": "148.222.71.12", "Email": "[email protected]", "Expiration Date": "20…

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

4 Nov 2026, 09:03 UTCAnonymous Poll67 voters

NEXT KOUN SA API LEAK KARU ? πŸ’€

  1. EAT TOKEN --> ACCESS+JWT TOKEN28%
  2. CRAFTLAND CREATOR INFO34%
  3. OUTFIT API31%
  4. LEVEL CHECK API31%

The shares total 124%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only β€” there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 18 most recent posts we hold, published 6 October 2026 to 7 November 2026. Telegram labels each poll by kind β€” an anonymous poll, a quiz, a closed set of final results β€” and that label is reproduced rather than paraphrased.

Forward network

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

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 8 November 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπ™Žπ˜Όπ™‚π˜Όπ™ π˜Όπ™‹π™„π™Ž πŸ”₯” (@SagarApis), 391 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/SagarApis.

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.