biztrac. BETA
COMPANY REGISTER PROFILE
882457672 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

AKTIV BYGG AS

Org. no. 882457672 Limited company (AS) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 402.4m
Operating profit NOK 8.6m
Equity NOK 21.8m
Incorporated 2000
Employees 52
Share capital NOK 321,000

AKTIV BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 882457672. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2000 and has 52 registered employees. Registered share capital is NOK 321,000, divided into 10165 shares. The company's stated purpose is: “Bygg- og anleggsvirksomhet samt vedlikehold av nærings- og boligeiendommer, og alt som hører naturlig dermed.”. The most recent filed accounts, for the 2025 financial year, show NOK 402.4m in revenue and NOK 8.6m in operating profit.

Key figures · 2025

Revenue
NOK 402.4m
▼ −25 %
Operating profit
NOK 8.6m
▼ −74 %
Equity
NOK 21.8m
▼ −59 %
Est. value
NOK 65.6m

Financial health · 2025

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns AKTIV BYGG AS?

AKTIV BYGG AS
NOK 402.4m rev. · NOK 8.6m profit

AKTIV BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKTIV BYGG AS

Who owns AKTIV BYGG AS?

VOKSTR AS is the largest registered owner, with 100.0%.

What is the revenue of AKTIV BYGG AS?

AKTIV BYGG AS had revenue of NOK 402.4m in 2025.

Who is the general manager of AKTIV BYGG AS?

Ronny Horni is registered as general manager of AKTIV BYGG AS.

Where is AKTIV BYGG AS based?

AKTIV BYGG AS has its business address in Oslo.

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

Report a problem

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