BIZTRAC BETA
Restaurant activities

HALVORSEN CAFE OG CATERING AS

Org. no. 927814870 Limited company (AS) Aurskog-Høland Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 641,000
Equity NOK 464,000
Incorporated 2021
Employees 9
Share capital NOK 30,000

HALVORSEN CAFE OG CATERING AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 927814870. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Servering og catering til mennesker.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 641,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
Operating profit
NOK 641,000
Equity
NOK 464,000
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns HALVORSEN CAFE OG CATERING AS?

IVETA CAIKAUSKIENE
HALVORSEN CAFE OG CATERING AS
NOK 9.4m rev. · NOK 641,000 profit

HALVORSEN CAFE OG CATERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HALVORSEN CAFE OG CATERING AS

Who owns HALVORSEN CAFE OG CATERING AS?

IVETA CAIKAUSKIENE is the largest registered owner, with 100.0%.

What is the revenue of HALVORSEN CAFE OG CATERING AS?

HALVORSEN CAFE OG CATERING AS had revenue of NOK 9.4m in 2025.

Who is the general manager of HALVORSEN CAFE OG CATERING AS?

Iveta Caikauskiene is registered as general manager of HALVORSEN CAFE OG CATERING AS.

Where is HALVORSEN CAFE OG CATERING AS based?

HALVORSEN CAFE OG CATERING AS has its business address in Løken.

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.