biztrac. BETA
COMPANY REGISTER PROFILE
921677278 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

H OLSEN SVEBERG AS

Org. no. 921677278 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 7.8m
Operating profit NOK 5.5m
Equity NOK 7.6m
Incorporated 2018
Share capital NOK 44,000

H OLSEN SVEBERG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 921677278. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 44,000, divided into 100 shares. The company's stated purpose is: “Investeringer i eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.8m in revenue and NOK 5.5m in operating profit.

Former names: SHN TOMT 13 AS, RISHAUG EIENDOM INVEST I AS

Key figures · 2025

Revenue
NOK 7.8m
▲ +3 %
Operating profit
NOK 5.5m
▲ +6 %
Equity
NOK 7.6m
▲ +5 %
Est. value
NOK 15.9m

Financial health · 2025

Liquidity
0.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
10.8%
Satisfactory
Equity as a share of total capital

Who owns H OLSEN SVEBERG AS?

H OLSEN SVEBERG AS
NOK 7.8m rev. · NOK 5.5m profit

H OLSEN SVEBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about H OLSEN SVEBERG AS

Who owns H OLSEN SVEBERG AS?

H OLSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of H OLSEN SVEBERG AS?

H OLSEN SVEBERG AS had revenue of NOK 7.8m in 2025.

Who is the general manager of H OLSEN SVEBERG AS?

Lars Brekke Olsen is registered as general manager of H OLSEN SVEBERG AS.

Where is H OLSEN SVEBERG AS based?

H OLSEN SVEBERG AS has its business address in Tiller.

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.