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

SIVSØR AS

Org. no. 996736997 Limited company (AS) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 8.6m
Operating profit NOK 399,000
Equity NOK 1.0m
Incorporated 2011
Employees 6
Share capital NOK 100,000

SIVSØR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 996736997. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre selskaper. Utleie og salg av eiendom. Selskapet skal også drive med grave- og grunnarbeider samt tjenester tilknyttet dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.6m in revenue and NOK 399,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.6m
▲ +19 %
Operating profit
NOK 399,000
▲ +106 %
Equity
NOK 1.0m
▲ +35 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
17.8%
Very good
Return on total assets
Solidity
36.5%
Good
Equity as a share of total capital

Who owns SIVSØR AS?

SIVSØR AS
NOK 8.6m rev. · NOK 399,000 profit

SIVSØR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIVSØR AS

Who owns SIVSØR AS?

Sverre Selli is the largest registered owner, with 50.0%.

What is the revenue of SIVSØR AS?

SIVSØR AS had revenue of NOK 8.6m in 2025.

Who is the general manager of SIVSØR AS?

Sverre Selli is registered as general manager of SIVSØR AS.

Where is SIVSØR AS based?

SIVSØR AS has its business address in Trondheim.

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.