BIZTRAC BETA
Other building and industrial cleaning activities

LILLEHAMMER VINDUSPUSS AS

Org. no. 830529292 Limited company (AS) Lillehammer Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 546,000
Equity NOK 676,000
Incorporated 2022
Share capital NOK 30,000

LILLEHAMMER VINDUSPUSS AS is registered as a limited company in Lillehammer, Innlandet with organisation number 830529292. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Utvendig og innvendig rengjøring av bygg som blant annet omfatter vindusvask, fasadespyling og takvask.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 546,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 546,000
Equity
NOK 676,000
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns LILLEHAMMER VINDUSPUSS AS?

EIRIK HAUKLIEN
LILLEHAMMER VINDUSPUSS AS
NOK 4.5m rev. · NOK 546,000 profit

LILLEHAMMER VINDUSPUSS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER VINDUSPUSS AS

Who owns LILLEHAMMER VINDUSPUSS AS?

EIRIK HAUKLIEN is the largest registered owner, with 40.0%.

What is the revenue of LILLEHAMMER VINDUSPUSS AS?

LILLEHAMMER VINDUSPUSS AS had revenue of NOK 4.5m in 2025.

Who is the general manager of LILLEHAMMER VINDUSPUSS AS?

Eirik Hauklien is registered as general manager of LILLEHAMMER VINDUSPUSS AS.

Where is LILLEHAMMER VINDUSPUSS AS based?

LILLEHAMMER VINDUSPUSS 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.