BIZTRAC BETA
Contract catering service activities and other food service activities

OSLO KANTINER AS

Org. no. 918166122 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −182,000
Equity NOK −2.1m
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−182k kr).

OSLO KANTINER AS is registered as a limited company in Oslo, Oslo with organisation number 918166122. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av kantiner, catering og andre relaterte bransjer. Selskapet skal ha mulighet til å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −182,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −182,000
Equity
NOK −2.1m

Financial health · 2024

Liquidity
17.71
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-270.2%
Weak
Equity as a share of total capital

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

Who owns OSLO KANTINER AS?

OSLO LUNSJ AS
OSLO KANTINER AS
NOK 1.5m rev. · NOK −182,000 profit

OSLO KANTINER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO KANTINER AS

Who owns OSLO KANTINER AS?

OSLO LUNSJ AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO KANTINER AS?

OSLO KANTINER AS had revenue of NOK 1.5m in 2024.

Where is OSLO KANTINER AS based?

OSLO KANTINER 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.