How-to Day change Marketwatch Kite

How to fix Day's change showing incorrect vs previous close on Kite

From WebNotes, a public knowledge base. Last updated . Reading time ~3 min.

When the day’s change column on the Kite marketwatch shows a value that does not match what you compute by subtracting the LTP from the previous close, the cause is almost always a corporate-action adjustment, a session phase issue, or a brief data-feed lag.

Conflict-of-interest disclosure. This guide is published by WebNotes Editorial Team for informational purposes. WebNotes has no commercial relationship with Zerodha.

Step-by-step procedure

Six diagnostic steps per the procedure infobox. The notes below explain each cause.

Cause 1: ex-date adjustment

The single most common cause. On the ex-date for a corporate action (dividend, bonus, split, rights), the official previous close is adjusted by the action amount. For example:

  • Pre-action previous close: Rs 1,000.
  • Dividend Rs 20 per share.
  • Adjusted previous close on ex-date: Rs 980.

If the stock opens at Rs 985, the day’s change is +Rs 5 (+0.51%), not -Rs 15 (-1.5%). Kite shows the official adjusted-previous-close-based change.

Look for the event tag on the row to confirm an action is in effect.

Cause 2: pre-open session

During pre-open (09:00 to 09:08 for equity), the “LTP” is the indicative open price built up from accumulated orders. This is not a real traded price. The change column can swing during pre-open as more orders arrive.

After 09:15, the change column stabilises against the official previous close.

Cause 3: stale browser cache

A change in previous-close data that arrives after browser load may not propagate to the displayed value until refresh. Ctrl+Shift+R / Cmd+Shift+R forces a fresh fetch.

Cause 4: F&O previous close = settlement, not LTC

For F&O contracts, previous close is the prior day’s settlement price (a weighted average over the last half hour of trading) rather than the last traded price. The change you compute manually from the marketwatch close may differ from what Kite shows because Kite uses settlement.

Cause 5: bhav copy publishing lag

NSE / BSE publish the next day’s previous-close in the bhav copy, typically around 18:30-19:00 IST. Between market close (15:30) and bhav copy publish, the previous-close value Kite shows is the current day’s close, but the next day’s previous-close has not yet been finalised. This rarely surfaces a discrepancy, but can do so for forced corporate actions processed late.

Cause 6: F&O contract maturity day

On the last trading day for an F&O contract, the previous close and the final settlement can be the same number or different. Final settlement uses the underlying’s closing value (averaged over the last half hour), which can differ from the contract’s previous close.

When to actually report

A persistent mismatch that does not resolve via refresh or bhav-copy cross-check, especially during normal market hours, may indicate a Kite-side data issue. In that case:

  1. Note the exact scrip, time, and the Kite-shown value.
  2. Compare against the live NSE / BSE quote on the exchange website.
  3. Submit a ticket via Console > Support.

See also

External references

References

  1. NSE India, Corporate action ex-date adjustment methodology, nseindia.com.
  2. Zerodha Support, Day’s change anomalies and ex-date handling, support.zerodha.com.
  3. SEBI (LODR) Regulations, 2015, schedule III.

Related articles

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.