BIZTRAC BETA
Ventilation installation

GRANLUND INNEKLIMA AS

Org. no. 927401398 Limited company (AS) Kongsvinger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 25,000
Equity NOK 132,000
Incorporated 2021
Share capital NOK 46,000

GRANLUND INNEKLIMA AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 927401398. The business is classified under ventilation installation (NACE 43.223). The company was incorporated in 2021. Registered share capital is NOK 46,000, divided into 1000 shares. The company's stated purpose is: “Servicearbeid på ventilasjonsanlegg og andre inneklimaprodukter samt salg av konsulenttimer, herunder også deltagelse i annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 25,000
Equity
NOK 132,000
Est. value
NOK 131,000

Financial health · 2024

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

Who owns GRANLUND INNEKLIMA AS?

LARS THOMAS JOHANSEN GRANLUND
GRANLUND INNEKLIMA AS
NOK 2.4m rev. · NOK 25,000 profit

GRANLUND INNEKLIMA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GRANLUND INNEKLIMA AS

Who owns GRANLUND INNEKLIMA AS?

LARS THOMAS JOHANSEN GRANLUND is the largest registered owner, with 60.0%.

What is the revenue of GRANLUND INNEKLIMA AS?

GRANLUND INNEKLIMA AS had revenue of NOK 2.4m in 2025.

Who is the general manager of GRANLUND INNEKLIMA AS?

Lars Thomas Johansen Granlund is registered as general manager of GRANLUND INNEKLIMA AS.

Where is GRANLUND INNEKLIMA AS based?

GRANLUND INNEKLIMA AS has its business address in Kongsvinger.

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.