BIZTRAC BETA
Restaurant activities

LUNSJBAR'N AS

Org. no. 932184761 Limited company (AS) Rakkestad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 4.0m
Operating profit NOK −98,000
Equity NOK −204,000
Incorporated 2023
Employees 11
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−204k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−98k kr).

LUNSJBAR'N AS is registered as a limited company in Rakkestad, Østfold with organisation number 932184761. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av mat og drikke og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.0m in revenue and NOK −98,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.0m
Operating profit
NOK −98,000
Equity
NOK −204,000

Financial health · 2024

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

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

Who owns LUNSJBAR'N AS?

HEGE BARBRO HAUG
LUNSJBAR'N AS
NOK 4.0m rev. · NOK −98,000 profit

LUNSJBAR'N AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNSJBAR'N AS

Who owns LUNSJBAR'N AS?

HEGE BARBRO HAUG is the largest registered owner, with 50.0%.

What is the revenue of LUNSJBAR'N AS?

LUNSJBAR'N AS had revenue of NOK 4.0m in 2024.

Who is the general manager of LUNSJBAR'N AS?

Marianne Bjørgen is registered as general manager of LUNSJBAR'N AS.

Where is LUNSJBAR'N AS based?

LUNSJBAR'N AS has its business address in Rakkestad.

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.