BIZTRAC BETA
Rental and operating of own or leased real estate

SVERRESBORG EIENDOM AS

Org. no. 977491525 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 2.3m
Equity NOK 40.9m
Incorporated 1997
Share capital NOK 200,000

SVERRESBORG EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 977491525. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 200,000. The company's stated purpose is: “Selskapets virksomhet er å utvikle, eie og drifte fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 2.3m
Equity
NOK 40.9m
Est. value
NOK 32.0m

Financial health · 2024

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.6%
Very good
Equity as a share of total capital

Who owns SVERRESBORG EIENDOM AS?

NORGESGRUPPEN EIENDOM MIDT-NORGE AS
SVERRESBORG EIENDOM AS
NOK 7.2m rev. · NOK 2.3m profit

SVERRESBORG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SVERRESBORG EIENDOM AS er morselskap for 249 datterselskaper:

Frequently asked questions about SVERRESBORG EIENDOM AS

Who owns SVERRESBORG EIENDOM AS?

NORGESGRUPPEN EIENDOM MIDT-NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of SVERRESBORG EIENDOM AS?

SVERRESBORG EIENDOM AS had revenue of NOK 7.2m in 2024.

Who is the general manager of SVERRESBORG EIENDOM AS?

Gorm Jorreng Ruud is registered as general manager of SVERRESBORG EIENDOM AS.

Where is SVERRESBORG EIENDOM AS based?

SVERRESBORG EIENDOM 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 15.06.2026.

Report a problem

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