Madhur is the awkward one. The schedule carries it as two markets — Madhur Day, open 13:30 and closing 14:30 IST, and Madhur Night, open 20:30 and closing 22:30 — and those two rows are not built to the same shape. The day session lasts sixty minutes; the night session lasts a hundred and twenty. Group every market on the board by its leading word and you get eight families with more than one row; in seven of them the two main legs run for the same number of minutes. Madhur is the eighth. That single asymmetry is the most useful thing a Madhur strategy can be built on, because it is the one difference between the two rows that changes what you can actually do — and it changes nothing at all about what either of them will produce.
The three things to settle before reading a Madhur chart. Name the row — "Madhur" is not a market here and no address will resolve it. Name the leg's clock — sixty minutes and a hundred and twenty minutes are not the same decision window. Name the denominator — declarations recorded, not days elapsed, and never the two rows added together.
Two Rows, And A Name That Resolves To Nothing
Every Madhur question starts with a small correction: there is no market stored under the name "Madhur". The two rows carry the suffix on both legs, so the bare family word is not an address — it is a search that fails.
| Stored name | Type | Open (IST) | Close (IST) | Session | Chart address |
|---|---|---|---|---|---|
| Madhur Day | MAIN | 13:30 | 14:30 | 60 minutes | /chart/jodi/madhur-day |
| Madhur Night | MAIN | 20:30 | 22:30 | 120 minutes | /chart/jodi/madhur-night |
Ask the chart route for the family and it stops you: /chart/jodi/madhur returns HTTP 404 with "Market not found", and so does /chart/pana/madhur. There is no third Madhur row either — no Starline sibling, which puts this family in the same two-row bracket as Sridevi and Dadar. The contrast with Sridevi is the part worth memorising, because the two families fail in opposite directions: Sridevi's day row is stored with no suffix, so its plain name silently means one specific market, while Madhur's plain name means nothing. Both are correct behaviour; neither is forgiving. The naming mechanics are worked through in the Sridevi analysis.
Four addresses cover the whole family — jodi and pana for each leg — and each is a separate record with its own weekly grid. If a link, a screenshot or a forwarded list says "the Madhur chart", it is either a guess or an abbreviation of one of those four.
The Only Family On The Board Whose Legs Differ
This is not a Madhur quirk that happens to exist; it is a Madhur quirk that exists once. Grouping all 31 seeded rows by their leading word and comparing the two MAIN legs gives the following, measured from the stored open and close times:
| Family | MAIN legs | Session lengths | Equal? |
|---|---|---|---|
| Madhur | Day + Night | 60 min / 120 min | No — the only mismatch on the board. |
| Sridevi | (bare) + Night | 60 min / 60 min | Yes. |
| Parel | Day + Night | 60 min / 60 min | Yes. |
| Milan, Rajdhani, Supreme, Kalyan, Dadar | Day + Night each | 120 min / 120 min | Yes, in all five. |
Read the table the right way round and it settles a question people usually answer from vibes. Session length is not a market-quality signal — seventeen MAIN rows run a hundred and twenty minutes, six run sixty, and the outliers are Gali at 55 and Main Bazar at 135. Length is a property of the schedule, and on this board it is a property the two halves of Madhur do not share. Any habit you build on one leg therefore has to be re-checked against the other before you carry it across, because the one structural input you would expect to be constant is not.
What The Sixty-Minute Difference Actually Changes
It changes the clock you can act on, and nothing else. The platform resolves each market row into one of three states against the IST clock — before the open time, between the open and close times, and after the close time — and the two betting families have different deadlines inside that sequence. An open-session position is only accepted while the row is still before its open time. A close-session position stays acceptable right up to the close time, and the moment a leg's number is actually declared the door shuts regardless of what the clock says, because a published result overrides the schedule. The state machine and the way declaration beats timer are set out in the Milan day and night analysis.
| Clock position | Madhur Day | Madhur Night |
|---|---|---|
| Before open | Until 13:30 | Until 20:30 |
| Open, session not yet closed | 13:30 → 14:30 — 60 minutes | 20:30 → 22:30 — 120 minutes |
| After close | 14:30 onward | 22:30 onward |
The middle row is the whole difference. That band is where the open number gets published, and it is also the only window in which you can see the open and still place against the close. On Madhur Day that is sixty minutes end to end; on Madhur Night it is twice that. So the asymmetry is not "the night market gives you more information" — both legs reveal exactly one open number and produce exactly one close number. It is that the night leg gives you twice the time to act on the same single fact, and the day leg gives you half. If your routine involves looking at the open before deciding, the day leg is where that routine gets tight, and it is worth timing yourself once rather than assuming.
One honest negative belongs here, because it is the exception that would break the table: the code has a branch for markets whose open time falls after their close time — the overnight rows that roll past midnight into the next logical date. On the current schedule none of the 31 rows triggers it; every seeded market opens before it closes, including both Madhur legs. The midnight case exists in the software and does not apply to today's board.
Where Each Leg Sits In The Day
The two rows also land in completely different traffic, which matters for reading rather than for predicting.
- Madhur Day closes a run, it does not start one. At 13:30 there are three MAIN rows live — Time Bazar, Parel Day and Madhur Day itself, all of them sixty-minute sessions. Their close times then fall out at fifteen-minute intervals: 14:00, 14:15, 14:30. Madhur Day is last, and for the fifteen minutes after Parel Day closes it is one of only two MAIN rows still open. Three results to reconcile inside half an hour is a transcription problem, not a market problem.
- Madhur Night closes into a queue. It opens at 20:30 with four MAIN rows live and closes at 22:30 with eight still open — Supreme Night closes ten minutes after it, and by 23:00 three more land in the same minute. The arithmetic behind that evening density, and why a night result is the one most often mis-recorded, is in the Rajdhani analysis.
Neither leg's draws are affected by the crowd around them. What is affected is how reliably you capture the number afterwards, and the two legs fail in different ways: the day leg gets reconciled late in a batch, the night leg gets reconciled from memory at the end of a long evening.
Reading The Two Charts Without Mixing Them
The page refuses an ambiguous name. The public results feed does the opposite, and this is where Madhur records quietly get pooled.
The feed tries an exact, case-insensitive name and, when that fails, falls back to a contains match and keeps whichever row the database happens to return first — no ordering is requested. So /api/result/madhur answers success: true even though no market is called "Madhur", having picked one of the two legs for you. It is looser than that again: /api/result/hur also succeeds, because "hur" is a substring of "Madhur". And it is inconsistent in the other direction — /api/result/madhur-day reports "Market not found", because the feed does not fold hyphens into spaces the way the chart page does, while /api/result/madhur day with a real space resolves.
Three consequences for anyone keeping Madhur numbers:
- Read the payload, not the request. Every item the feed returns carries the resolved market's own name. That field is the only evidence of which leg you were given, and it is the first thing to check.
- An empty array is not a clean answer. It can mean the leg has no records in the window exactly as easily as it can mean you never asked for the leg you thought you did.
- A placeholder is not a gap. Where a leg has no stored number, the feed substitutes a placeholder string rather than dropping the row, so a half-declared day comes back looking complete. What the placeholder marks, and which of them are permanent, is defined in the terminology guide.
The two surfaces also look back different distances from today — the chart grids and the feed do not cover the same span, and both windows slide forward a day at a time. That difference is quantified in the Rajdhani piece linked above; the point here is only that a Madhur figure is meaningless without the surface it came from.
What A Madhur Strategy Can Honestly Cover
The word "strategy" earns its place here in one sense only: a written process for deciding, per leg, before the numbers arrive. Anything aimed at forecasting the numbers themselves runs into arithmetic that does not care which row you chose.
- The base rate is identical for both legs. A specific two-digit combination is one of a hundred, so a week of seven declarations on Madhur Day and a week of seven on Madhur Night are samples of the same size from the same distribution. What you should expect to see in a sample that small — including the absences that read as cold streaks — is worked out in the weekly chart analysis guide.
- Two rows, two samples, never one. Each Madhur leg produces at most one declaration a day, so each carries roughly 365 dated rows a year and the pair does not add up to 730 observations of anything. They share a word.
- A blank is a fact about the schedule, not the market. A day nobody declared is absent from the grid rather than recorded as zero, and a weekday switched off applies to one row and not its sibling — so Madhur Day and Madhur Night can legitimately have different running-day sets in the same week.
- The only real per-leg difference is time. Sixty minutes against a hundred and twenty. Plan the decision window, not the odds.
A Two-Leg Review Sheet
Seven lines, filled once a week, and every claim above becomes checkable against your own records:
- Leg. Day or Night — one word, and it decides which grid you opened.
- Address used. The chart page or the feed, because they do not return the same span.
- Date read. The window moves daily, so an undated count is not reproducible.
- Declarations counted. Dated rows that actually carried a number, out of the days available.
- Expectation. What the base rate said should appear in that many draws — written down before you counted.
- Decision window used. Whether you acted on the open number inside the leg's clock, and how much of it you needed.
- Verdict. Keep the rule or drop it. A rule that is never dropped is not being tested.
Four weeks of that, kept apart per leg, and most "Madhur patterns" die on the sheet rather than in your bankroll. That is the intended outcome.
Frequently Asked Questions
Is Madhur Day the same market as Madhur Night?
No. They are two separate rows with separate open and close times, separate archives and separate weekly grids, and neither is a session of the other. The only thing they share is the leading word.
Why does the Madhur chart not open when I search for "Madhur"?
Because no market is stored under that name. Both rows carry a suffix, so the family word matches nothing and the chart page returns "Market not found". Use madhur-day or madhur-night.
Which one is the better market to follow?
Neither — the draws are the same kind of event in both. The honest difference is the decision window: sixty minutes on the day leg against a hundred and twenty on the night leg. Pick the leg whose clock fits the hour you can actually watch.
Does the longer session mean more results?
No. Each row produces at most one declaration per day whatever its session length. A hundred and twenty minutes is more time to act, not more data to analyse.
Can I combine the two Madhur charts into one trend?
You can, and the result describes neither market. It mixes a midday declaration with an evening one across two different schedules, and it halves the effective history behind any claim you make from it.
Why does my Madhur result look blank on one day?
Either that day was never declared, in which case it is simply absent from the grid, or one leg of it is stored without a number, in which case a placeholder is shown. Both are records about the schedule rather than about the draw.
Is there a Madhur Starline market?
Not on this board. The Starline rows belong to Kalyan, Mumbai, Milan, Rajdhani, Supreme and Parel, and a Starline market has no jodi to chart in any case.
Where do the Madhur numbers come from?
Each dated row stores a three-digit open pana and a three-digit close pana, and everything else on the grid — the pair formed from them and the single digits — is computed from those six digits afterwards. The chart is a view over that record, not a separate source.