BIZTRAC BETA
Buying and selling of own real estate

STENBORG EIENDOM AS

Org. no. 830776842 Limited company (AS) Sarpsborg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 2.0m
Equity NOK 1.0m
Incorporated 2023
Share capital NOK 30,000

STENBORG EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 830776842. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse. -bedriftsrådgivning og annen administrativ rådgivning -gi støtte til veldedige og allmennyttige formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 2.0m
Equity
NOK 1.0m
Est. value
NOK 4.1m

Financial health · 2024

Liquidity
6.24
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.2%
Satisfactory
Equity as a share of total capital

Who owns STENBORG EIENDOM AS?

HÅVAR ÅDALEN HOLDING AS
STENBORG EIENDOM AS
NOK 2.2m rev. · NOK 2.0m profit

STENBORG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENBORG EIENDOM AS

Who owns STENBORG EIENDOM AS?

HÅVAR ÅDALEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STENBORG EIENDOM AS?

STENBORG EIENDOM AS had revenue of NOK 2.2m in 2024.

Who is the general manager of STENBORG EIENDOM AS?

Håvar Ådalen is registered as general manager of STENBORG EIENDOM AS.

Where is STENBORG EIENDOM AS based?

STENBORG EIENDOM AS has its business address in Sarpsborg.

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.