BIZTRAC BETA
Civil engineering activities

SIVILINGENIØR SVERRE STEEN AS

Org. no. 968662635 Limited company (AS) Fredrikstad Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 451,000
Operating profit NOK 30,000
Equity NOK 73,000
Incorporated 1994
Share capital NOK 100,000

SIVILINGENIØR SVERRE STEEN AS is registered as a limited company in Fredrikstad, Østfold with organisation number 968662635. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet samt annen virksomhet som naturlig faller inn under dette, herunder delta i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 451,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2025

Revenue
NOK 451,000
Operating profit
NOK 30,000
Equity
NOK 73,000
Est. value
NOK 192,000

Financial health · 2025

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.9%
Weak
Equity as a share of total capital

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

Who owns SIVILINGENIØR SVERRE STEEN AS?

SVERRE STEEN
SIVILINGENIØR SVERRE STEEN AS
NOK 451,000 rev. · NOK 30,000 profit

SIVILINGENIØR SVERRE STEEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIVILINGENIØR SVERRE STEEN AS

Who owns SIVILINGENIØR SVERRE STEEN AS?

SVERRE STEEN is the largest registered owner, with 100.0%.

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

SIVILINGENIØR SVERRE STEEN AS had revenue of NOK 451,000 in 2025.

Where is SIVILINGENIØR SVERRE STEEN AS based?

SIVILINGENIØR SVERRE STEEN AS has its business address in Fredrikstad.

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.