BIZTRAC BETA
Development of building projects

STEO EIENDOM AS

Org. no. 984845537 Limited company (AS) Larvik Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 902,000
Operating profit NOK 422,000
Equity NOK −245,000
Incorporated 2002
Share capital NOK 380,000

Signals

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

STEO EIENDOM AS is registered as a limited company in Larvik, Vestfold with organisation number 984845537. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2002. Registered share capital is NOK 380,000, divided into 3800 shares. The company's stated purpose is: “Eie, drive og utvikle faste eiendommer, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 902,000 in revenue and NOK 422,000 in operating profit.

Key figures · 2024

Revenue
NOK 902,000
Operating profit
NOK 422,000
Equity
NOK −245,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
3.28
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.8%
Weak
Equity as a share of total capital

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

Who owns STEO EIENDOM AS?

STEO INVEST AS
STEO EIENDOM AS
NOK 902,000 rev. · NOK 422,000 profit

STEO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEO EIENDOM AS

Who owns STEO EIENDOM AS?

STEO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STEO EIENDOM AS?

STEO EIENDOM AS had revenue of NOK 902,000 in 2024.

Who is the general manager of STEO EIENDOM AS?

Tommy Ulseth is registered as general manager of STEO EIENDOM AS.

Where is STEO EIENDOM AS based?

STEO EIENDOM AS has its business address in Larvik.

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.