BIZTRAC BETA
Holiday and other short-stay accommodation

LILLEHAMMER TRADISJONSHÅNDVERK AS

Org. no. 926575791 Limited company (AS) Lillehammer Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 999,000
Operating profit NOK 42,000
Equity NOK 143,000
Incorporated 2021
Share capital NOK 30,000

LILLEHAMMER TRADISJONSHÅNDVERK AS is registered as a limited company in Lillehammer, Innlandet with organisation number 926575791. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Tømrerarbeid, lafting, restaurering, tradisjonshåndverk, samt alt som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 999,000 in revenue and NOK 42,000 in operating profit.

Key figures · 2024

Revenue
NOK 999,000
Operating profit
NOK 42,000
Equity
NOK 143,000
Est. value
NOK 231,000

Financial health · 2024

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

Who owns LILLEHAMMER TRADISJONSHÅNDVERK AS?

KARL EMIL ENGEN
LILLEHAMMER TRADISJONSHÅNDVERK AS
NOK 999,000 rev. · NOK 42,000 profit

LILLEHAMMER TRADISJONSHÅNDVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER TRADISJONSHÅNDVERK AS

Who owns LILLEHAMMER TRADISJONSHÅNDVERK AS?

KARL EMIL ENGEN is the largest registered owner, with 50.0%.

What is the revenue of LILLEHAMMER TRADISJONSHÅNDVERK AS?

LILLEHAMMER TRADISJONSHÅNDVERK AS had revenue of NOK 999,000 in 2024.

Where is LILLEHAMMER TRADISJONSHÅNDVERK AS based?

LILLEHAMMER TRADISJONSHÅNDVERK 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.