BIZTRAC BETA
COMPANY REGISTER PROFILE
815859472 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

KÅRE SIVERTSEN AS

Org. no. 815859472 Limited company (AS) Trondheim Incorporated 1976 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 1.3m
Equity NOK 2.2m
Incorporated 1976
Share capital NOK 100,000

KÅRE SIVERTSEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 815859472. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1976. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive utleievirksomhet av fast eiendom i Trondheim, investeringsvirksomhet og annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 1.3m
Equity
NOK 2.2m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns KÅRE SIVERTSEN AS?

ROLF SIVERTSEN
KÅRE SIVERTSEN AS
NOK 3.1m rev. · NOK 1.3m profit

KÅRE SIVERTSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KÅRE SIVERTSEN AS

Who owns KÅRE SIVERTSEN AS?

ROLF SIVERTSEN is the largest registered owner, with 100.0%.

What is the revenue of KÅRE SIVERTSEN AS?

KÅRE SIVERTSEN AS had revenue of NOK 3.1m in 2025.

Who is the general manager of KÅRE SIVERTSEN AS?

Rolf Sivertsen is registered as general manager of KÅRE SIVERTSEN AS.

Where is KÅRE SIVERTSEN AS based?

KÅRE SIVERTSEN AS has its business address in Heimdal.

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.