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

BORGGATEN 7 KULTUR-EIENDOM AS

Org. no. 912484572 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 9.5m
Operating profit NOK 3.7m
Equity NOK 684,000
Incorporated 2013
Share capital NOK 607,000

BORGGATEN 7 KULTUR-EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 912484572. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 607,000, divided into 606942 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 9.5m in revenue and NOK 3.7m in operating profit.

Key figures · 2025

Revenue
NOK 9.5m
▲ +1 %
Operating profit
NOK 3.7m
▲ +2 %
Equity
NOK 684,000
▼ −58 %
Est. value
NOK 7.8m

Financial health · 2025

Liquidity
0.69
Weak
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
2.5%
Not satisfactory
Equity as a share of total capital

Who owns BORGGATEN 7 KULTUR-EIENDOM AS?

BORGGATEN 7 KULTUR-EIENDOM AS
NOK 9.5m rev. · NOK 3.7m profit

BORGGATEN 7 KULTUR-EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGGATEN 7 KULTUR-EIENDOM AS

Who owns BORGGATEN 7 KULTUR-EIENDOM AS?

BORGGATA 7-9 INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BORGGATEN 7 KULTUR-EIENDOM AS?

BORGGATEN 7 KULTUR-EIENDOM AS had revenue of NOK 9.5m in 2025.

Where is BORGGATEN 7 KULTUR-EIENDOM AS based?

BORGGATEN 7 KULTUR-EIENDOM AS has its business address in Oslo.

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.