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

OLAVSKVARTALET AS

Org. no. 926352040 Limited company (AS) Trondheim Incorporated 2020 Active
Revenue 2025 NOK 4.9m
Operating profit NOK 3.6m
Equity NOK 598,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-18 Adresseendring registrert 2026-06-18.

OLAVSKVARTALET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926352040. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 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.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 3.6m in operating profit.

Former names: OLAVSKVARTALET INVEST AS

Key figures · 2025

Revenue
NOK 4.9m
▲ +10 %
Operating profit
NOK 3.6m
▲ +27 %
Equity
NOK 598,000
▼ −61 %
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
10.4%
Satisfactory
Equity as a share of total capital

Who owns OLAVSKVARTALET AS?

OLAVSKVARTALET AS
NOK 4.9m rev. · NOK 3.6m profit

OLAVSKVARTALET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAVSKVARTALET AS

Who owns OLAVSKVARTALET AS?

INDIGO MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of OLAVSKVARTALET AS?

OLAVSKVARTALET AS had revenue of NOK 4.9m in 2025.

Where is OLAVSKVARTALET AS based?

OLAVSKVARTALET 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.