BIZTRAC BETA
Restaurant activities

KOLONIALEN CAFE AS

Org. no. 923155112 Limited company (AS) Arendal Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK −188,000
Equity NOK 5,000
Incorporated 2019
Employees 14
Share capital NOK 76,000

Signals

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

KOLONIALEN CAFE AS is registered as a limited company in Arendal, Agder with organisation number 923155112. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 14 registered employees. Registered share capital is NOK 76,000, divided into 760 shares. The company's stated purpose is: “Drift av cafe og cateringdrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK −188,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK −188,000
Equity
NOK 5,000
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
0.33
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KOLONIALEN CAFE AS?

ROLF BIRGER ÅNONSEN
KOLONIALEN CAFE AS
NOK 3.7m rev. · NOK −188,000 profit

KOLONIALEN CAFE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOLONIALEN CAFE AS

Who owns KOLONIALEN CAFE AS?

ROLF BIRGER ÅNONSEN is the largest registered owner, with 50.0%.

What is the revenue of KOLONIALEN CAFE AS?

KOLONIALEN CAFE AS had revenue of NOK 3.7m in 2025.

Who is the general manager of KOLONIALEN CAFE AS?

Linda Bjørkholt-Boiling is registered as general manager of KOLONIALEN CAFE AS.

Where is KOLONIALEN CAFE AS based?

KOLONIALEN CAFE AS has its business address in Bjorbekk.

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.