BIZTRAC BETA
Other technical consultancy

INNREGULERING AS

Org. no. 919306394 Limited company (AS) Holmestrand Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 296,000
Equity NOK −152,000
Incorporated 2017
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−152k kr).

INNREGULERING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 919306394. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2017. Registered share capital is NOK 150,000, divided into 100 shares. The company's stated purpose is: “Innregulering av varme og kjøling av VVS-anlegg og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 296,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
Operating profit
NOK 296,000
Equity
NOK −152,000
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-29.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INNREGULERING AS?

ROGER GURVIN IVERSEN
INNREGULERING AS
NOK 6.7m rev. · NOK 296,000 profit

INNREGULERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INNREGULERING AS

Who owns INNREGULERING AS?

ROGER GURVIN IVERSEN is the largest registered owner, with 100.0%.

What is the revenue of INNREGULERING AS?

INNREGULERING AS had revenue of NOK 6.7m in 2025.

Who is the general manager of INNREGULERING AS?

Roger Gurvin Iversen is registered as general manager of INNREGULERING AS.

Where is INNREGULERING AS based?

INNREGULERING AS has its business address in Sande I Vestfold.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.