biztrac. BETA
COMPANY REGISTER PROFILE
923275401 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other new goods

KIØSTERUDGÅRDEN AS

Org. no. 923275401 Limited company (AS) Oslo Incorporated 2019 Active
Revenue 2025 NOK 141,000
Operating profit NOK −369,000
Equity NOK 213,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−369k kr).

KIØSTERUDGÅRDEN AS is registered as a limited company in Oslo, Oslo with organisation number 923275401. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie, kunstpresentasjoner, servering, samt hva som hermed står i forbindelse, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 141,000 in revenue and NOK −369,000 in operating profit.

Key figures · 2025

Revenue
NOK 141,000
▼ −74 %
Operating profit
NOK −369,000
▼ −445 %
Equity
NOK 213,000
▲ +108 %
Est. value
NOK 147,000

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
-3.0%
Not satisfactory
Return on total assets
Solidity
1.8%
Not satisfactory
Equity as a share of total capital

Who owns KIØSTERUDGÅRDEN AS?

KIØSTERUDGÅRDEN AS
NOK 141,000 rev. · NOK −369,000 profit

KIØSTERUDGÅRDEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIØSTERUDGÅRDEN AS

Who owns KIØSTERUDGÅRDEN AS?

MERKANTILBYGG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KIØSTERUDGÅRDEN AS?

KIØSTERUDGÅRDEN AS had revenue of NOK 141,000 in 2025.

Where is KIØSTERUDGÅRDEN AS based?

KIØSTERUDGÅRDEN 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.