biztrac. BETA
COMPANY REGISTER PROFILE
979380267 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

SIVILINGENIØR SVERRE CHRISTENSEN AS

Org. no. 979380267 Limited company (AS) Frogn Incorporated 1997 Active
Revenue 2025 NOK 4.1m
Operating profit NOK 3.5m
Equity NOK 12.6m
Incorporated 1997
Share capital NOK 30,000

SIVILINGENIØR SVERRE CHRISTENSEN AS is registered as a limited company in Frogn, Akershus with organisation number 979380267. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1997. Registered share capital is NOK 30,000, divided into 50 shares. The company's stated purpose is: “Utleie, investeringer, pluss konsulentvirksomhet, prosjektadministrasjon og byggeledelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 3.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
▲ +200 %
Operating profit
NOK 3.5m
▲ +263 %
Equity
NOK 12.6m
▲ +26 %
Est. value
NOK 15.4m

Financial health · 2025

Liquidity
7.08
Very good
Current assets ÷ current liabilities
Profitability
33.6%
Very good
Return on total assets
Solidity
90.1%
Very good
Equity as a share of total capital

Who owns SIVILINGENIØR SVERRE CHRISTENSEN AS?

SIVILINGENIØR SVERRE CHRISTENSEN AS
NOK 4.1m rev. · NOK 3.5m profit

SIVILINGENIØR SVERRE CHRISTENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIVILINGENIØR SVERRE CHRISTENSEN AS

Who owns SIVILINGENIØR SVERRE CHRISTENSEN AS?

Sverre Johan Christensen is the largest registered owner, with 100.0%.

What is the revenue of SIVILINGENIØR SVERRE CHRISTENSEN AS?

SIVILINGENIØR SVERRE CHRISTENSEN AS had revenue of NOK 4.1m in 2025.

Where is SIVILINGENIØR SVERRE CHRISTENSEN AS based?

SIVILINGENIØR SVERRE CHRISTENSEN AS has its business address in Drøbak.

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.