BIZTRAC BETA
Forging and shaping metal and powder metallurgy

GNOSJÖ KONSTSMIDE NORGE AS

Org. no. 992746084 Limited company (AS) Hamar Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK −518,000
Equity NOK 749,000
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−518k kr).

GNOSJÖ KONSTSMIDE NORGE AS is registered as a limited company in Hamar, Innlandet with organisation number 992746084. The business is classified under forging and shaping metal and powder metallurgy (NACE 25.400). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tilvirkning og salg av elektriske belysningsprodukter, hagemøbler og hageutstyr samt deltakelse i dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK −518,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK −518,000
Equity
NOK 749,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns GNOSJÖ KONSTSMIDE NORGE AS?

GNOSJ KONSTMIDE AKTIEBOLAG
GNOSJÖ KONSTSMIDE NORGE AS
NOK 2.9m rev. · NOK −518,000 profit

GNOSJÖ KONSTSMIDE NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GNOSJÖ KONSTSMIDE NORGE AS

Who owns GNOSJÖ KONSTSMIDE NORGE AS?

GNOSJ KONSTMIDE AKTIEBOLAG is the largest registered owner, with 100.0%.

What is the revenue of GNOSJÖ KONSTSMIDE NORGE AS?

GNOSJÖ KONSTSMIDE NORGE AS had revenue of NOK 2.9m in 2024.

Where is GNOSJÖ KONSTSMIDE NORGE AS based?

GNOSJÖ KONSTSMIDE NORGE AS has its business address in Hamar.

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.