KongZanaTrading live room plus strategy | Trading Reviews and Vendors

futures.io - futures trading strategies, market news, trading charts and platforms

Trading Reviews and Vendors

Discuss and review vendors of commercial trading products, trading rooms and services, trading indicators or third-party paid add-ons


KongZanaTrading live room plus strategy

  #14 (permalink)

Elite Member
Miami, Florida
Trading Experience: Advanced
Platform: Ninjatrader, Ninjabroker
Broker/Data: NINJABROKER, Continuum, KINETICK
Favorite Futures: NQ ES TF CL GC
Posts: 11 since Aug 2010
Thanks: 4 given, 11 received


I took the the 14 day trial and have since taken a paid subscription. The room opens about 8:30/8:45 EST and he spends the first couple of hours calling trades and then another hour answering questions and reviewing that morning's signals. He has three active trading charts, TF NQ and DAX.

Each morning an email is sent out that contains the also targets for the various contracts currently TF ES NQ YM DAX GC and CL. They need to be applied to their respective charts and the best way to do that is to use Ninja's retracement lines from their tool box. See attachment.

KongZanaTrading live room plus strategy-2015-10-26_14-29-59.pdf

His primary Kongzana indicator is a histogram at bottom of chart with with an MA of sorts that gives the signals at different points when they cross or it crosses the zero line. The charts use Fat Tails VWAP and Pivot Points.

Valdemar calls his signals in real time so everything is in plain sight and real time. Just bear in mind that he uses the sim mode for orders so real order entry/exits might not always match the comparable ones on a sim account. For learning the process it is recommended taking trades only in the direction of the trend(signal line on the histogram). Also I would suggest concentrating on just one contract at the outset until you fully understand the trading system.

Reply With Quote
The following 8 users say Thank You to 2KEY for this post:
Page generated 2019-04-25 in 0.07 seconds with 12 queries on phoenix