BIZTRAC BETA
COMPANY REGISTER PROFILE
922163251 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Site preparation

LILLEHAMMER GRUS AS

Org. no. 922163251 Limited company (AS) Lillehammer Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 417,000
Operating profit NOK 320,000
Equity NOK 1.0m
Incorporated 2018
Share capital NOK 200,000

LILLEHAMMER GRUS AS is registered as a limited company in Lillehammer, Innlandet with organisation number 922163251. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Gruvedrift, utvinning av stein og grusforekomster og anleggsrørleggervirksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 417,000 in revenue and NOK 320,000 in operating profit.

Key figures · 2025

Revenue
NOK 417,000
Operating profit
NOK 320,000
Equity
NOK 1.0m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
4.47
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.2%
Very good
Equity as a share of total capital

Who owns LILLEHAMMER GRUS AS?

GEIR ARILD KARLSEN
LILLEHAMMER GRUS AS
NOK 417,000 rev. · NOK 320,000 profit

LILLEHAMMER GRUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEHAMMER GRUS AS

Who owns LILLEHAMMER GRUS AS?

GEIR ARILD KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of LILLEHAMMER GRUS AS?

LILLEHAMMER GRUS AS had revenue of NOK 417,000 in 2025.

Who is the general manager of LILLEHAMMER GRUS AS?

Geir Arild Karlsen is registered as general manager of LILLEHAMMER GRUS AS.

Where is LILLEHAMMER GRUS AS based?

LILLEHAMMER GRUS AS has its business address in Fåberg.

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.