BIZTRAC BETA
Rental and operating of own or leased real estate

FLAKK KAUPANGEN AS

Org. no. 925949183 Limited company (AS) Ålesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −204,000
Equity NOK 334,000
Incorporated 2020
Share capital NOK 300,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−204k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FLAKK KAUPANGEN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 925949183. 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 300,000, divided into 1000 shares. The company's stated purpose is: “Utleie av næringslokaler.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −204,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −204,000
Equity
NOK 334,000
Est. value
NOK 305,000

Financial health · 2024

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

Who owns FLAKK KAUPANGEN AS?

FLAKK EIENDOM AS
FLAKK KAUPANGEN AS
NOK 0 rev. · NOK −204,000 profit

FLAKK KAUPANGEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FLAKK KAUPANGEN AS er morselskap for 7 datterselskaper:

Frequently asked questions about FLAKK KAUPANGEN AS

Who owns FLAKK KAUPANGEN AS?

FLAKK EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FLAKK KAUPANGEN AS?

FLAKK KAUPANGEN AS had revenue of NOK 0 in 2024.

Where is FLAKK KAUPANGEN AS based?

FLAKK KAUPANGEN AS has its business address in Ålesund.

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.