Status
Not open for further replies.
ST,

Will you please explain? IMO, if executed at 5305, I shouldn't worry about that as much as I should have in case of 3516 or 4516... :rofl::rofl::rofl:
Dreamer,

Point of worry is not at what price order got executed.... point of worry is tht if it has happened once, it can happen again...

point of worry is tht u were taken out of ur trade without ur choice....
 

TheDreamer

Well-Known Member
Dreamer,

Point of worry is not at what price order got executed.... point of worry is tht if it has happened once, it can happen again...

point of worry is tht u were taken out of ur trade without ur choice....

Akash,

Choice is the last thing I have in my mind after an order is given to the system or when it gets executed... i have no control over the markets...

While trading you may worry about thousands of things... So, if it happens, one should remain prepared... I hope you were present in the wild swing days of 2008 or October 2010, when 40 points up/down used to happen within a minute... :)

P.S. - These freak trades happen, has happened and will also happen in the future... be prepared... Can give example of Reliance which happened in 2010...

BTW, thinking of taking an initiative to send e-mails to the concerned authorities regarding this incident... Is it possible to send individual mails by the members of Traderji to these people?
 
Last edited:
:(:(:clap::confused:Dear Sir,
I requested for commodity pay out on 29.03.12, but the same was not done till now. Please, do the needfull and make payment by 31.03.12 positively.
With Regards

Chinmoy Biswas
MHDC0007
 

megapixel

Well-Known Member
I have encountered this type of problem in NSE pathsala.

guys , don't trust SL-M and SL-L orders.

check out NSE pathsala and test few executions and you'll see how they behave :)

buggy system works
 

Zerodha

Well-Known Member
About the Freak trade triggering the stop losses....

After looking at all the posts, firstly let me clear the confusion out which some of you seem to have...

1. Mininifty did trade at 3500, but none of the Zerodha client actually bought or sold mininifty at that price... Even the trade that got executed at 3500, was later reversed by the exchange...

2. The problem was, because it ticked at 3500, it triggered a lot of Stop losses placed in the system... Even if it was not 3500 and it was 5000, it would have still triggered all the stops...

What do I think about it??

Stock or commodity markets are uncertain and not under control of anyone... If an index like s&P could have ticked 10% down because of a freakish incident last year, nifty which turns over 1/10th of S&P and mininifty probably 1/1000th, it is no big deal... It wasn't a big deal for even the news to flash it...

These are the risks we take trading financial markets and we have to live with it. No complain to anyone will help. Markets move based on the balance of buyers and sellers. If someone decides to sell a million lots of nifty futures, he might bring it down by 10% for a few minutes... WE can't tell this guy who wants to sell not to sell...

Yesterday's incident, for every guy who probably lost a little money because of this trade, there was probably another guy who made the same...

Remember guys, the ticker is always right... If a price was recorded on the tape, no one can fight it... We just have to get used to the fact that, **** Happens !!! and move on.... ;)...
 

Zerodha

Well-Known Member
Re: Zerodha: Freak Trade in Minifty Triggering Stop Loss

Such a thing happened to me recently (with Zerodha). I was in a long trade and put in a SL-M order. CMP was way above my SL-M and suddenly SL was triggered and my position was closed. As per tick data of Zerodha and Sharekhan the low price for the minute when the SL-M was triggered was clearly ABOVE my SL-M.
I immediately called Zerodha and asked for a clarification and after several calls back and forth here's what they told me:

"NSE tick data does not record ALL trades. Instead NSE records trades at an interval of 3 seconds. Whatever it records at those 3 second intervals is the tick data. IF within those 3 seconds a trade happens at a FAR off value, it will trigger stops but that FAR off value is not listed in the NSE statistics for that minute."

It is scary to say the least. It's strange. It's unbelievable. However I left it at that as at this stage my time is better spent learning to trade than fixing systems beyond my comprehension.

Zerodha, Seniors will have to comment on the 3 second interval and the whole issue.
Hey Shridhar,

I remember talking to you about this incident, if I am not wrong...

Yesterday's 3500 tick was probably not shown on a lot of charting softwares... You could probably check it out... That is what I was trying to tell you the last time.... Just because your charting software didn't show the tick, doesn't mean it didn't happen....

When I said 3 ticks( Not seconds), I meant speed of updating of your charting software.. For every 10 ticks on NSE,you probably get to see only 2 or 3...

During this 10 ticks, if some tick doesn't show on your charting software, you can't really blame anyone for that... If you want tick by tick data from NSE, costs quite a bit....All the recorded ticks can be checked anyways on the NSE website....

Guys, please understand this!!! be it any member of NSE/BSE/MCX, if a trade was executed in your account, you can be rest assured, it really happened... There is no conspiracy theory around it...
 

soft_trader

Well-Known Member
About the Freak trade triggering the stop losses....

After looking at all the posts, firstly let me clear the confusion out which some of you seem to have...

1. Mininifty did trade at 3500, but none of the Zerodha client actually bought or sold mininifty at that price... Even the trade that got executed at 3500, was later reversed by the exchange...

2. The problem was, because it ticked at 3500, it triggered a lot of Stop losses placed in the system... Even if it was not 3500 and it was 5000, it would have still triggered all the stops...

What do I think about it??


These are the risks we take trading financial markets and we have to live with it. No complain to anyone will help. Markets move based on the balance of buyers and sellers. If someone decides to sell a million lots of nifty futures, he might bring it down by 10% for a few minutes... WE can't tell this guy who wants to sell not to sell...

Remember guys, the ticker is always right... If a price was recorded on the tape, no one can fight it... We just have to get used to the fact that, **** Happens !!! and move on.... ;)...
Zerodha,

I am sorry to say that I can't agree with you. How it is possible to generate a tick in Minifty by NSE beyond the circuit limit? You only told that there was a tick at 3500, how the hell it is possible?

Try to understand it technically, before generating the tick of 3500, a circuit breaker should come into effect, which should stop the trading on the scrip with immediate effect.

So, with a price band of 10% how the tick gets generated at 3500? Do you have any answer for that?

And if it is so, then that means the circuit breaker is of no use, tomorrow another programming bug in NSE could bring down the price of Nifty at 10 or even at 1 point????

So where is the efficiency of the circuit breaker here???

Zerodha, please answer.
 
Hey,

Did you get a way to sort this out?

I am using Wave II and getting the same problem only in the trade section of the NSE NOW mobile and not in the market data.

If it can be resolved then it will save me from the panic of buying another mobile. What was your experience?

Thanks in anticipation
Options pro

Sachin,

The exact error message that I get when I try to login to TRADE section using Samsung Monte is:

Sorry, your phone does not have appropriate certificate to make connection with the server (E212)

Do you know what can be done to resolve this error?

I have installed the Java version on the phone, and the "Market Data" section of the application that does not require login works absolutely fine. The problem is only when I try to log into the "Trade" section.
 
Status
Not open for further replies.

Similar threads