Population 48,664 puts Rimouski 18th of 23 in Quebec and at 1% of the rostered provincial total. Every downstream assumption in Rimouski — absorption pace, achievable rent, lender appetite — tracks that scale more closely than it tracks the zone code printed on the Rimouski map.

Across the 134-market Canadian roster, Rimouski is 95th by population and shares tier 3 with 78 other markets. Its 0.03× ratio to Montréal is the number to apply before importing any Montréal rent or velocity assumption into a Rimouski model.

Rimouski sits between Shawinigan at 49,620 and Victoriaville at 47,523. Same province, same rules, different scale: the cleanest way to test whether a Rimouski density assumption is ambitious or ordinary.

The nearest national peers to Rimouski by size and tier are Cornwall, ON, Woodstock, ON, Brandon, MB. Cornwall in particular, at 47,845, is close enough in scale that its approval timelines are a reasonable prior for Rimouski — a prior, not evidence.

No Rimouski zone has cleared review yet, so this page publishes no Rimouski regulatory figure at all. That is the publishability gate working rather than an oversight: with no reviewed row, the Rimouski page stays out of the sitemap and carries a noindex directive.

Coverage policy does not bend for Rimouski. Across the 134 rostered markets, including Rimouski, indexation needs two independent conditions — the tier gate permitting the pair, and a promoted row with provenance. Rimouski's tier-3 status limits it to anchor products.

Every published Rimouski row is dated deliberately: bylaws change, and an undated figure is a rumour. Find a discrepancy against the current Rimouski — Planning and Development text and the Rimouski row gets re-read or pulled.

Coverage also has a ceiling in ambition, not just in law. There are more zone codes in Rimouski than any small team can verify at once, so review is prioritised by the codes most likely to carry a real Rimouski project — the mixed-use and multi-unit districts rather than the exhaustive tail.

Zoning exists in Rimouski because la Loi sur l'aménagement et l'urbanisme delegates the power to Rimouski — Planning and Development. That delegation is conditional: the Rimouski instrument, un règlement de zonage, must conform to un plan d'urbanisme, and where the two conflict the policy document wins. It is why an FSR read off a Rimouski zoning map can sit below what the plan contemplates — the plan is the ceiling of ambition, the bylaw the ceiling of right.

When the Rimouski bylaw falls short of what a site needs, the ordinary routes are a dérogation mineure for marginal gaps and a rezoning for structural ones. A refusal or an unacceptable condition on a Rimouski application is contested at the borough or municipal council, with registry and referendum steps for certain amendments. In Rimouski that choice is a scheduling question first: relief is measured in months, a rezoning in years, and carry does not pause for either.

Within Rimouski, base zoning is only the first layer. Site-specific amendments, heritage controls, holding symbols and overlay districts attach to individual parcels, which is why two adjacent Rimouski lots under the same code can support materially different buildings. Confirm the parcel with Rimouski — Planning and Development, not the colour on the map.

Rimouski does not control the whole stack. Changes at the Quebec level flow through la Loi sur l'aménagement et l'urbanisme into what Rimouski — Planning and Development may or must permit, and the Rimouski bylaw text often lags the statute. That lag is exactly where a stale Rimouski feasibility gets expensive.

Two ceilings compete on every Rimouski parcel: lot area × FSR, and footprint × storeys after setbacks and coverage. The calculator resolves both from your inputs and reports the binding one, because relief only helps a Rimouski applicant if it lifts the constraint that is actually binding.

As a worked illustration on a 28,000 sf Rimouski site at 2 FSR, the ceiling is 56,000 sf and roughly 60 units at 800 sf net of an 85% efficiency factor. Substitute the real Rimouski figures from un règlement de zonage before treating any of it as a Rimouski result.

The bind flag is the whole point of a Rimouski run. If height binds a Rimouski site, an FSR bonus buys nothing and the conversation with Rimouski — Planning and Development is about storeys or floor-to-floor efficiency. If FSR binds, extra Rimouski height buys nothing either — the same area lands on a smaller plate, usually at a higher cost per square foot.

Parking is the third constraint and the most often mispriced in Rimouski. The tool converts a Rimouski parking ratio into stalls from the unit count implied by your GFA and unit size, then shows what those stalls displace. Excavation and below-grade structure are volatile line items in Quebec, so a ratio that looks trivial can decide a Rimouski site.

Before comparing a Rimouski figure to one from another province, check the definition. Rimouski — Planning and Development may exclude parking, mechanical space or below-grade area from the Rimouski floor-area calculation, and a 2.0 that excludes those is a materially larger building than a 2.0 that does not.

Height is equally slippery in Rimouski. A limit expressed in metres, in storeys, or as a geometric envelope produces different buildings on the same Rimouski lot, and the calculator here converts between them using the floor-to-floor figure you supply rather than assuming one.

Rimouski footprint is the smaller of the setback-derived area and the coverage cap. Which one governs depends on parcel geometry, not on policy, and it flips between neighbouring Rimouski lots more often than most owners expect.

The Rimouski unit count falls out of GFA divided by average unit size after an efficiency factor, and the parking obligation follows from there. It is the shortest chain on the page and the one where a careless Rimouski assumption does the most damage.

Zoning sets the ceiling in Rimouski; absorption decides whether reaching it is wise. A Rimouski envelope that pencils at full permitted density still has to sell or lease into a market of 48,664, and that constraint is not written in any bylaw Rimouski — Planning and Development publishes.

Where Rimouski demand is uncertain, staging beats maximising. It trades scale economies for optionality, and in a 95th-ranked market that trade is usually the right one.

The comparison table gives Rimouski a reference set that is not simply the nearest city. Similar-sized markets are the better analogue, because Rimouski demand tracks scale more closely than geography.

The most common way a Rimouski feasibility goes wrong is not arithmetic, it is staleness. un règlement de zonage is amended on Rimouski — Planning and Development's schedule, not yours, so a Rimouski figure carried from a file six months old may already be void. The printed summary from this page carries its own date for exactly that reason.

Because Rimouski runs at 0.03× Montréal, its liquidity is thinner: an entitlement error in Rimouski takes longer to trade out of, and the discount demanded is steeper than the Quebec leader would face on the same file.

This is a Rimouski screening instrument, not an entitlement opinion. Every figure should be re-read against un règlement de zonage and confirmed with Rimouski — Planning and Development before money moves.

Three kinds of information appear on the Rimouski page and they are kept apart on purpose: roster facts common to all 134 markets, Quebec statutory structure, and reviewed Rimouski bylaw readings. Only the third is ever presented as a local regulatory figure.

Under the gate, Rimouski either has a cited figure or it has none. Half-verified Rimouski data is treated as no data, and the page carries a noindex directive rather than a hedge.

Rimouski outputs carry a provenance label so a reader never has to guess. Observed Rimouski values cite a document and a date; modelled values are arithmetic on the numbers you entered, and are presented as such.