Telegram RegisterThe public register of Telegram

Channel

NikkahGram Female Profiles

@nikkahgramfemales

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Cite this entry

1,712subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002114229711
TypeChannel
Username@nikkahgramfemales
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 11 August 2026
On Telegramt.me/nikkahgramfemales

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@nikkahgrammales/201121 Apr 2026, 15:05 UTC@nikkahgramfemales/1917 · this entry21 Apr 2026, 15:06 UTC1.00under a minute
@nikkahgrammales/20164 May 2026, 14:09 UTC@nikkahgramfemales/1923 · this entry4 May 2026, 17:02 UTC1.002.9 hours
@nikkahgrammales/201716 May 2026, 13:17 UTC@nikkahgramfemales/1924 · this entry16 May 2026, 13:17 UTC1.00under a minute
@nikkahgrammales/202115 Jun 2026, 08:29 UTC@nikkahgramfemales/1933 · this entry16 Jun 2026, 11:56 UTC1.0027 hours
@nikkahgramfemales/1935 · this entry30 Jun 2026, 17:21 UTC@nikkahgrammales/202330 Jun 2026, 17:21 UTC1.00under a minute
@nikkahgrammales/20241 Aug 2026, 18:50 UTC@nikkahgramfemales/1937 · this entry1 Aug 2026, 18:53 UTC1.003 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@nikkahgrammales7 (7/7 hand-verifiable sample passed)1.00under a minute@nikkahgrammales (52)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 5 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 9 April 2026 to 1 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @nikkahgramfemales — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

1,7121,7131,712.57 Aug 2026, 22:46 — 1,713 subscribers8 Aug 2026, 07:25 — 1,712 subscribers7 Aug 2026, 22:468 Aug 2026, 07:25
2 measurements taken within a single day, net -1. 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 1,712–1,713 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 07:251,712-1
7 Aug 2026, 22:461,713first reading

Engagement

20 posts held, back to 9 April 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
22.2%
avg views ÷ 1,712 subscribers
Avg views / post
380
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 1 August 2026
Posts held20 (9 April 20261 August 2026)
Views total380
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 22:46 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.

Reaction mix

92 reactions across 14 posts, in 9 distinct kinds. The most used accounts for 59.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5559.8%
👍1415.2%
😐88.70%
🔥55.43%
🤨44.35%
💯22.17%
😱22.17%
🤩11.09%
🤯11.09%

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 15 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 92reactions 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 9 April 2026 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.

Recent posts

1 Aug 2026, 18:53 UTC380 viewsread 7 August 2026

Nikkahgram App has received another update, now available in most regions on iOS and Android. Download now to get a bunch of new features including free usage for Sisters, expanded marriage focus options, better filters, clear settings controls and much more. Our Instant-Matches are back too, so make sure you've added references to increase your chances of finding a suitable spouse.

30 Jun 2026, 17:21 UTC≈1,380 views9 reactionsread 7 August 2026

All new candidate profiles are now only visible in our App! Download now, search: NikkahGram - FREE basic use for brothers and up to FREE Premium use for sisters, find out more on our website.

😐81

22 Jun 2026, 20:47 UTC≈1,780 views1 reactionsread 7 August 2026

Download our updated App (iOS or Android) ASAP to get access to your matches. Many legacy profiles are recieving matches but don't know because they just haven't logged in! It's quick and easy, sign in with your email address and get Free access to proceed! Details available on our website NikkahGram.com

1

16 Jun 2026, 11:56 UTC≈1,970 views3 reactionsread 7 August 2026

Don't let matches expire! Download the App and respond within the 7 days you get. If candidates request to match with you and you don't reply, the match will expire and you won't be able to match with that user again! So make sure to log in and respond in time so you don't miss out on candidates who you may have been interested in. Remember, your legacy system profile is already active in the App so will likely be g

🤨2👍1

13 Jun 2026, 11:23 UTCviews —

NikkahGram Female Profiles pinned «Assalaamu'alaikum, please download the latest updated version of our App (iOS or Android) to get all of the improvements like In-app subscriptions, FREE access for all Sisters including Premium tier for some, Simplified registration, Notification indicators…»

13 Jun 2026, 11:23 UTC≈1,900 views0 reactionsread 7 August 2026

Just another reminder to download our latest NikkahGram app version and log in with your existing email address. If your details are on the system already, you'll be able to match straight away! Otherwise you can register for a free account (brothers and sisters). Check SPAM/JUNK for the OTP code if not received when signing up, and subscribe in-app. Remember to check your emails from info@nikkahgram.com about prof

6 Jun 2026, 23:24 UTC≈2,260 views6 reactionsread 7 August 2026

Assalaamu'alaikum, please download the latest updated version of our App (iOS or Android) to get all of the improvements like In-app subscriptions, FREE access for all Sisters including Premium tier for some, Simplified registration, Notification indicators, and many quality-of-life fixes. Plus, all legacy profiles have now been fully imported to the App and activated. Just log in with your existing email address to

6

19 May 2026, 06:18 UTC≈2,520 views9 reactionsread 7 August 2026

🧕 Female candidate for NikkahGram! 🔍 Candidate ID: peBQEY8 🎂 Current age: 22 💍 Marital status: Never Married - 👰‍♀️ Marital Stance: Chastity 🚸 Children: None - 🏳️ Ethnic Origin: Pakistan 🇵🇰: Indian/ Pakistani 🪪 Citizenship/Nationality: United States 🇺🇸 📍 Location/Residence: Saudi Arabia 🇸🇦: Jeddah 🕒 Settled Since: Over 10 years 📌 Raised In: Saudi Arabia 🇸🇦 📏 Height: 5ft1 to 5ft2 ⚖️ Weight: 61–65kg 👗 Physique: Toned

5🔥3👍1

16 May 2026, 18:51 UTC≈2,050 views6 reactionsread 7 August 2026

🧕 Female candidate for NikkahGram! 🔍 Candidate ID: LDWOBQ2 🎂 Current age: 29 💍 Marital status: Never Married - 👰‍♀️ Marital Stance: Polygyny 🚸 Children: 1 - A boy & i’m the only one caring for him. Dad is out of the picture. 🏳️ Ethnic Origin: Ghana 🇬🇭: Wala 🪪 Citizenship/Nationality: Ghana 🇬🇭 📍 Location/Residence: Ghana 🇬🇭: Westlands 🕒 Settled Since: 1 to 4 years 📌 Raised In: Ghana 🇬🇭 📏 Height: 5ft9 or above ⚖️ Wei

5👍1

16 May 2026, 13:17 UTC≈1,940 views1 reactionsread 7 August 2026

Assalaamu'alaikum. If you have been unable to enter your phone number when logging into our Nikkahgram app or you cannot verify it via OTP, please WhatsApp Us (NikkahGram) using the phone number registered on your profile, so we can verify it and allow you to register easily.

👍1

4 May 2026, 17:02 UTC≈2,530 viewsread 7 August 2026

Reminder for all current users: Please log in to the App and validate your profiles as the time limit will be expiring soon. Sisters: If you are not yet signed up, you can usually do so in-app directly on Android or iOS. Brothers: Please pay on our website before attempting to make a profile as it won't be possible otherwise.

1 May 2026, 13:10 UTC≈2,630 views6 reactionsread 7 August 2026

🧕 Female candidate for NikkahGram! 🔍 Candidate ID: 5BK0kKd 🎂 Current age: 25 💍 Marital status: Divorced (Talaq) - It's been 2yrs ,he disrespected me while I was pregnant 👰‍♀️ Marital Stance: Revert 🚸 Children: 1 - He is two yrs old ,living with me 🏳️ Ethnic Origin: Kenya 🇰🇪: Kenyan 🪪 Citizenship/Nationality: Kenya 🇰🇪 📍 Location/Residence: Kenya 🇰🇪: Nairobi 🕒 Settled Since: 4 to 10 years 📌 Raised In: Kenya 🇰🇪 📏 Heig

4👍2

Showing the 12 most recent of 20 posts we hold for @nikkahgramfemales. 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“NikkahGram Female Profiles” (@nikkahgramfemales), 1,712 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/nikkahgramfemales.

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.