Multirange Indicator Highlighter: Days, Timezone, ColorMultirange Indicator Highlighter: Days, Timezone, Color
This indicator allows you to highlight up to 3 custom time ranges for every single day of the week (Monday–Sunday). It is perfect for marking Killzones, session opens, or specific volatility windows.
Key Features:
Daily Control: Separate toggles and settings for each day (Mon–Sun).
3 Ranges per Day: Independent start/end times and colors for each slot.
Flexible Format: Supports HH:MM input (e.g., 09:30-11:00).
Smart Timezones: Enter city names (e.g., America/New_York) or offsets (e.g., GMT+2) directly.
Compact UI: Clean, one-line settings for easy configuration.
How to use:
Set your timezone first, then enable the days and ranges you need. Adjust colors and transparency to keep your chart readable. Indicator
Time Range Marker By BCB ElevateThe Time Range Marker is a simple yet powerful visual tool for traders who want to focus on specific time intervals within the trading day. This indicator highlights a custom time range on your chart using a background color, helping you visually isolate key trading sessions or event windows such as:
Market open/close hours
News release periods
High-volatility trading zones
Personal strategy testing windows
⚙️ Key Features:
Customizable start and end time (hour & minute)
Works across all intraday timeframes
Adjustable highlight color to match your chart theme
Built using Pine Script v5 for speed and flexibility
🔧 Settings:
Start Hour / Minute – Set the beginning of the time range (in 24-hour format)
End Hour / Minute – Define when the range ends
Highlight Color – Choose the background color for better visibility
🕒 Timezone Note:
The indicator uses UTC time by default to ensure accuracy across markets. If your broker uses a different timezone (like EST, IST, etc.), the script can be adjusted to reflect your local market hours.
✅ How to Use the Time Range Marker Indicator
This indicator is used to visually highlight a specific time window each trading day, such as:
Market open or close sessions (e.g., NYSE, London, Tokyo)
High-impact news release periods
Custom time slots for strategy testing or scalping
🛠️ Installation Steps
Open PulseWire and go to any chart.
Click on Pine Editor at the bottom of the screen.
Copy and paste the full Pine Script (shared above) into the editor.
Click the “Add to Chart” ▶️ button.
The indicator will appear on the chart with a highlighted background during the time range you set.
⚙️ How to Customize the Time Range
After adding the indicator:
Click the gear icon ⚙️ next to the indicator’s name on the chart.
Adjust the following settings:
Start Hour / Start Minute: The beginning of your time range (in 24-hour format).
End Hour / End Minute: When the highlight should stop.
Highlight Color: Pick a color and transparency for visual clarity.
Click OK to apply changes.
🕒 Timezone Consideration
By default, the indicator uses UTC (Coordinated Universal Time).
To match your broker’s timezone (e.g., EST, IST, etc.), you'll need to adjust the script by changing:
sessStart = timestamp("Etc/UTC", ...)
sessEnd = timestamp("Etc/UTC", ...)
to your correct timezone, like "Asia/Kolkata" for IST or "America/New_York" for EST.
Let me know your broker or local timezone, and I’ll update it for you.
📈 Tips for Traders
Combine this with volume, price action, or breakout indicators to focus your strategy on high-probability time windows.
Use multiple versions of this script if you want to highlight more than one time range in a day.
Indicator
Indicator
Indicator
Indicator
chrono_utilsLibrary "chrono_utils"
📝 Description
Collection of objects and common functions that are related to datetime windows session days and time ranges. The main purpose of this library is to handle time-related functionality and make it easy to reason about a future bar checking if it will be part of a predefined session and/or inside a datetime window. All existing session functionality I found in the documentation e.g. "not na(time(timeframe, session, timezone))" are not suitable for strategy scripts, since the execution of the orders is delayed by one bar, due to the script execution happening at the bar close. Moreover, a history operator with a negative value that looks forward is not allowed in any pinescript expression. So, a prediction for the next bar using the bars_back argument of "time()"" and "time_close()" was necessary. Thus, I created this library to overcome this small but very important limitation. In the meantime, I added useful functionality to handle session-based behavior. An interesting utility that emerged from this development is data anomaly detection where a comparison between the prediction and the actual value is happening. If those two values are different then a data inconsistency happens between the prediction bar and the actual bar (probably due to a holiday, half session day, a timezone change etc..)
🤔 How to Guide
To use the functionality this library provides in your script you have to import it first!
Copy the import statement of the latest release by pressing the copy button below and then paste it into your script. Give a short name to this library so you can refer to it later on. The import statement should look like this:
import jason5480/chrono_utils/2 as chr
To check if a future bar will be inside a window first of all you have to initialize a DateTimeWindow object.
A code example is the following:
var dateTimeWindow = chr.DateTimeWindow.new().init(fromDateTime = timestamp('01 Jan 2023 00:00'), toDateTime = timestamp('01 Jan 2024 00:00'))
Then you have to "ask" the dateTimeWindow if the future bar defined by an offset (default is 1 that corresponds th the next bar), will be inside that window:
// Filter bars outside of the datetime window
bool dateFilterApproval = dateTimeWindow.is_bar_included()
You can visualize the result by drawing the background of the bars that are outside the given window:
bgcolor(color = dateFilterApproval ? na : color.new(color.fuchsia, 90), offset = 1, title = 'Datetime Window Filter')
In the same way, you can "ask" the Session if the future bar defined by an offset it will be inside that session.
First of all, you should initialize a Session object.
A code example is the following:
var sess = chr.Session.new().from_sess_string(sess = '0800-1700:23456', refTimezone = 'UTC')
Then check if the given bar defined by the offset (default is 1 that corresponds th the next bar), will be inside the session like that:
// Filter bars outside the sessions
bool sessionFilterApproval = view.sess.is_bar_included()
You can visualize the result by drawing the background of the bars that are outside the given session:
bgcolor(color = sessionFilterApproval ? na : color.new(color.red, 90), offset = 1, title = 'Session Filter')
In case you want to visualize multiple session ranges you can create a SessionView object like that:
var view = SessionView.new().init(SessionDays.new().from_sess_string('2345'), array.from(SessionTimeRange.new().from_sess_string('0800-1600'), SessionTimeRange.new().from_sess_string('1300-2200')), array.from('London', 'New York'), array.from(color.blue, color.orange))
and then call the draw method of the SessionView object like that:
view.draw()
🏋️♂️ Please refer to the "EXAMPLE DATETIME WINDOW FILTER" and "EXAMPLE SESSION FILTER" regions of the script for more advanced code examples of how to utilize the full potential of this library, including user input settings and advanced visualization!
⚠️ Caveats
As I mentioned in the description there are some cases that the prediction of the next bar is not accurate. A wrong prediction will affect the outcome of the filtering. The main reasons this could happen are the following:
Public holidays when the market is closed
Half trading days usually before public holidays
Change in the daylight saving time (DST)
A data anomaly of the chart, where there are missing and/or inconsistent data.
A bug in this library (Please report by PM sending the symbol, timeframe, and settings)
Special thanks to @robbatt and @skinra for the constructive feedback 🏆. Without them, the exposed API of this library would be very lengthy and complicated to use. Thanks to them, now the user of this library will be able to get the most, with only a few lines of code! Library
Indicator
Indicator
Indicator
Indicator
Strategy
