BIZTRAC BETA
Restaurant activities

BARRATT KAFEDRIFT AS

Org. no. 912316335 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 66,000
Operating profit NOK −274,000
Equity NOK −6.5m
Incorporated 2013
Share capital NOK 3.6m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−6,5 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−274k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BARRATT KAFEDRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 912316335. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013. Registered share capital is NOK 3.6m, divided into 30 shares. The company's stated purpose is: “Kafe og restaurantdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 66,000 in revenue and NOK −274,000 in operating profit.

Key figures · 2024

Revenue
NOK 66,000
Operating profit
NOK −274,000
Equity
NOK −6.5m

Financial health · 2024

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

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

Who owns BARRATT KAFEDRIFT AS?

MIF AS
BARRATT KAFEDRIFT AS
NOK 66,000 rev. · NOK −274,000 profit

BARRATT KAFEDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARRATT KAFEDRIFT AS

Who owns BARRATT KAFEDRIFT AS?

MIF AS is the largest registered owner, with 100.0%.

What is the revenue of BARRATT KAFEDRIFT AS?

BARRATT KAFEDRIFT AS had revenue of NOK 66,000 in 2024.

Where is BARRATT KAFEDRIFT AS based?

BARRATT KAFEDRIFT 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.