BIZTRAC BETA
Contract catering service activities and other food service activities

LØVETANN KANTINE AS

Org. no. 985883653 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 2.8m
Equity NOK 2.0m
Incorporated 2003
Employees 29
Share capital NOK 100,000

LØVETANN KANTINE AS is registered as a limited company in Oslo, Oslo with organisation number 985883653. The business is classified under contract catering service activities and other food service activities (NACE 56.220). The company was incorporated in 2003 and has 29 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive kantine- og cateringvirksomhet og matfaglige kurs i innland og utland og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
Operating profit
NOK 2.8m
Equity
NOK 2.0m
Est. value
NOK 9.4m

Financial health · 2025

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.9%
Good
Equity as a share of total capital

Who owns LØVETANN KANTINE AS?

LØVETANN HOLDING AS
LØVETANN KANTINE AS
NOK 12.9m rev. · NOK 2.8m profit

LØVETANN KANTINE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØVETANN KANTINE AS

Who owns LØVETANN KANTINE AS?

LØVETANN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LØVETANN KANTINE AS?

LØVETANN KANTINE AS had revenue of NOK 12.9m in 2025.

Who is the general manager of LØVETANN KANTINE AS?

Merete Anfinnsen is registered as general manager of LØVETANN KANTINE AS.

Where is LØVETANN KANTINE AS based?

LØVETANN KANTINE 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.