Investing LTP Holdings Marketwatch

LTP difference between Holdings and marketwatch on Kite

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

A common point of confusion: the LTP shown for a scrip on the Kite Holdings tab does not exactly match the LTP shown for the same scrip on the marketwatch . The discrepancy is small (usually a few paise to a few rupees) but is regularly reported as a “bug”. It is almost always explainable by one of a handful of causes.

The four common causes

1. Refresh timing

The marketwatch streams live ticks at sub-second frequency. The Holdings tab refreshes the LTP for each row at a slightly slower cadence (every few seconds, throttled to reduce server load). A quote that ticked one second ago will appear on the marketwatch immediately and on Holdings after a small delay.

This is the most common cause. The two views catch up within a few seconds.

2. Exchange dual-listing

If the same scrip is listed on NSE and BSE:

  • The marketwatch row may be the NSE row (you added the NSE listing).
  • The Holdings tab shows the demat holding, which is exchange-agnostic but the LTP is pulled from the exchange where you bought.

If you bought on NSE and the marketwatch row is BSE, both LTPs are valid but reference different exchange tapes. NSE and BSE prices for the same scrip can differ by a few paise to several rupees, especially in illiquid scrips.

See also: Holdings not displayed on exchange bought from .

3. End-of-day snapshot vs live tick

Outside market hours, Kite displays a previous-close snapshot. On Holdings, the snapshot may be the bhav copy close (T-1 official close from NSE). On the marketwatch, the last-streamed tick may differ by a few paise depending on when the stream stopped.

After market open, both converge as live ticks update.

4. Pre-market and post-close difference

During the pre-open session (09:00 to 09:08), the marketwatch shows the indicative open price; Holdings may continue to show the previous day’s close. Between 15:30 (market close) and the end-of-day batch (~16:00), the two views can also diverge briefly.

Day’s P&L impact

The day’s P&L on Holdings uses the LTP at the moment the column was refreshed. If the marketwatch LTP has since moved, the day’s P&L can look slightly stale by a few paise per share. This compounds across the portfolio but is rarely a meaningful number for retail investors.

See also: Day’s P&L on holdings calculation .

When the difference is large

A difference of more than 0.5% between Holdings and marketwatch LTP for the same scrip is unusual and warrants investigation:

  • Corporate action. A bonus, split or merger has changed the post-adjustment LTP, but one view may still show the pre-adjustment price. See event tag .
  • Suspended trading. One feed has stopped updating; the other shows the last live price.
  • Delisted scrip in Holdings. The Holdings tab continues to show the last LTP before delisting; the marketwatch row shows zero or is removed.
  • Different scrip on marketwatch. Verify the marketwatch row is the same ISIN / symbol as the holding.

When to act on a difference

If the difference exceeds a few rupees and persists for more than 30 seconds during normal market hours:

  • Hard-refresh Kite web.
  • Force-close and reopen the Kite app.
  • Cross-check with the live NSE / BSE quote on the exchange website.
  • If divergence persists, contact Zerodha support via Console.

See also

External references

References

  1. Zerodha Support, LTP discrepancies between Holdings and marketwatch, support.zerodha.com.
  2. NSE India, Quote and trade dissemination, nseindia.com.
  3. BSE India, Market data dissemination, bseindia.com.

Reviewed and published by

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.