BIZTRAC BETA
Sewerage

AKTIV RØRINSPEKSJON AS

Org. no. 981514122 Limited company (AS) Lørenskog Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 11.8m
Operating profit NOK 3.6m
Equity NOK 4.0m
Incorporated 2000
Employees 5
Share capital NOK 177,000

AKTIV RØRINSPEKSJON AS is registered as a limited company in Lørenskog, Akershus with organisation number 981514122. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2000 and has 5 registered employees. Registered share capital is NOK 177,000, divided into 3530 shares. The company's stated purpose is: “Rørinspeksjon, høytrykkspyling, rehabilitering av rørsystemer samt annet i denne forbindelse, herunder investeringer i andre selskaper, utleie av fast eiendom-herunder utleie av bolig, stallplass og beitemark.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.8m in revenue and NOK 3.6m in operating profit.

Key figures · 2025

Revenue
NOK 11.8m
Operating profit
NOK 3.6m
Equity
NOK 4.0m
Est. value
NOK 11.8m

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.2%
Good
Equity as a share of total capital

Who owns AKTIV RØRINSPEKSJON AS?

NAHME AS
AKTIV RØRINSPEKSJON AS
NOK 11.8m rev. · NOK 3.6m profit

AKTIV RØRINSPEKSJON AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKTIV RØRINSPEKSJON AS

Who owns AKTIV RØRINSPEKSJON AS?

NAHME AS is the largest registered owner, with 35.0%.

What is the revenue of AKTIV RØRINSPEKSJON AS?

AKTIV RØRINSPEKSJON AS had revenue of NOK 11.8m in 2025.

Who is the general manager of AKTIV RØRINSPEKSJON AS?

Hege Tomter is registered as general manager of AKTIV RØRINSPEKSJON AS.

Where is AKTIV RØRINSPEKSJON AS based?

AKTIV RØRINSPEKSJON AS has its business address in Lørenskog.

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.