BIZTRAC BETA
Rental and operating of own or leased real estate

KORSKIRKEKVARTALET AS

Org. no. 993595306 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 6.3m
Operating profit NOK 4.3m
Equity NOK 51.1m
Incorporated 2009
Share capital NOK 20.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KORSKIRKEKVARTALET AS is registered as a limited company in Bergen, Vestland with organisation number 993595306. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 20.0m, divided into 1 shares. The company's stated purpose is: “Investering i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse, herunder oppta lån for å finansiere denne virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.3m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 6.3m
Operating profit
NOK 4.3m
Equity
NOK 51.1m
Est. value
NOK 46.0m

Financial health · 2024

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

Who owns KORSKIRKEKVARTALET AS?

MAGIC NORWAY AS
KORSKIRKEKVARTALET AS
NOK 6.3m rev. · NOK 4.3m profit

KORSKIRKEKVARTALET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KORSKIRKEKVARTALET AS

Who owns KORSKIRKEKVARTALET AS?

MAGIC NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of KORSKIRKEKVARTALET AS?

KORSKIRKEKVARTALET AS had revenue of NOK 6.3m in 2024.

Where is KORSKIRKEKVARTALET AS based?

KORSKIRKEKVARTALET AS has its business address in Bergen.

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.