BIZTRAC BETA
Restaurant activities

EGON LILLEHAMMER AS

Org. no. 971175117 Limited company (AS) Lillehammer Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 34.8m
Operating profit NOK 4.2m
Equity NOK 1.3m
Incorporated 1994
Employees 23
Share capital NOK 106,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EGON LILLEHAMMER AS is registered as a limited company in Lillehammer, Innlandet with organisation number 971175117. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1994 and has 23 registered employees. Registered share capital is NOK 106,000, divided into 2650 shares. The company's stated purpose is: “Hotell og service virksomhet samt annen næringsvirksomhet”. The most recent filed accounts, for the 2024 financial year, show NOK 34.8m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 34.8m
Operating profit
NOK 4.2m
Equity
NOK 1.3m
Est. value
NOK 16.4m

Financial health · 2024

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.2%
Satisfactory
Equity as a share of total capital

Who owns EGON LILLEHAMMER AS?

PEELORG AS
EGON LILLEHAMMER AS
NOK 34.8m rev. · NOK 4.2m profit

EGON LILLEHAMMER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EGON LILLEHAMMER AS

Who owns EGON LILLEHAMMER AS?

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

What is the revenue of EGON LILLEHAMMER AS?

EGON LILLEHAMMER AS had revenue of NOK 34.8m in 2024.

Who is the general manager of EGON LILLEHAMMER AS?

Kim Andre Molnes is registered as general manager of EGON LILLEHAMMER AS.

Where is EGON LILLEHAMMER AS based?

EGON LILLEHAMMER AS has its business address in Lillehammer.

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.