/queue simple + /queue tree → ISP capacity planner

MikroTik QoS & Queue Calculator

Generate a PCQ-based plan for subscriber shaping. The form keeps upload and download explicit and shows whether you are building a Simple Queue or a Queue Tree that still needs matching packet marks.

Written by Diaa · Last reviewed 21 September 2026 · RouterOS v7 focus
Topology matters: this tool calculates queue values and produces a starting configuration. Queue Tree requires packet marks and correct parent interfaces. Do not paste it into production without checking packet direction and existing queues.

1. Traffic policy

Use Simple Queue when target-based shaping is enough. Use Queue Tree when you already have a deliberate Mangle/packet-mark design.

Use a stable name that matches your subscriber or plan.

Used directly by Simple Queue; document it for Queue Tree.

RouterOS accepts values such as 50M, 10M, or 512k.

Keep direction explicit; do not assume the interface perspective.

Queue Tree parents and marks

These marks must already be created by your Mangle rules. The generator does not invent a packet classification policy.

qos-plan.rsc
Edit the limits to rebuild the plan.


Simple Queue or Queue Tree?
A Simple Queue attaches a target address or subnet to a limit. It is easy to audit and is often the safer choice for small subscriber groups. A Queue Tree attaches child queues to an interface or global parent and normally relies on Mangle packet marks. It scales a different policy model, but a syntactically valid Queue Tree can still do nothing if the marks or parent direction are wrong.
Why the form asks for two limits
Download and upload travel in opposite directions. For a subscriber target, download is normally classified with the destination address and upload with the source address. In a Queue Tree, the correct classifier depends on where marking occurs and which interface is the parent. Always confirm with interface counters and one controlled test.
PCQ sizing
PCQ shares traffic between substreams using a classifier. This page sets pcq-rate to the plan limit as a clear starting point. If your policy is to let a group share a larger parent while each user receives a smaller ceiling, change the PCQ rate deliberately and document it; do not hide that decision in generated code.
Verification sequence
  1. Check that no older queue already shapes the same target or packet mark.
  2. Apply the queue with a known test subscriber and watch queue bytes and drops.
  3. Run a download and upload test separately; record the interface and queue counters.
  4. Test at least two subscribers if the policy is meant to share a parent.
  5. Keep a rollback command or export before changing an active ISP gateway.
Practical rule: if you cannot explain where a packet is marked, which parent it enters, and which direction its bytes take, use Simple Queue first and revisit Queue Tree after documenting the path.
Related tools
IPv4 CalculatorPlan customer pools and queue targets.Wireless Link BudgetCheck the radio link before blaming QoS.Deployment ChecklistRecord the change and rollback path.