BIZTRAC BETA
Wholesale of household, office and shop furniture, carpets and lighting equipment

GRO LAGER AS

Org. no. 895122602 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 467,000
Equity NOK 6.9m
Incorporated 2010
Share capital NOK 200,000

GRO LAGER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 895122602. The business is classified under wholesale of household, office and shop furniture, carpets and lighting equipment (NACE 46.470). The company was incorporated in 2010. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drive servicevirksomhet til hotell- og restaurantnæringen, i form av innkjøp, bearbeiding og videresalg av driftsmidler og lagerrekvisita, samt annen næringsvirksomhet som naturlig står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 467,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 467,000
Equity
NOK 6.9m
Est. value
NOK 5.1m

Financial health · 2024

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

Who owns GRO LAGER AS?

NORREIN HOLDING AS
GRO LAGER AS
NOK 2.3m rev. · NOK 467,000 profit

GRO LAGER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRO LAGER AS

Who owns GRO LAGER AS?

NORREIN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of GRO LAGER AS?

GRO LAGER AS had revenue of NOK 2.3m in 2024.

Who is the general manager of GRO LAGER AS?

Roger Halshamn is registered as general manager of GRO LAGER AS.

Where is GRO LAGER AS based?

GRO LAGER AS has its business address in Trondheim.

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.