BIZTRAC BETA
Manufacture of furniture

GJESDAL MØBEL AS

Org. no. 999073948 Limited company (AS) Gjesdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK −19,000
Equity NOK −573,000
Incorporated 2012
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−573k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

GJESDAL MØBEL AS is registered as a limited company in Gjesdal, Rogaland with organisation number 999073948. The business is classified under manufacture of furniture (NACE 31.000). The company was incorporated in 2012. Registered share capital is NOK 1.0m, divided into 50000 shares. The company's stated purpose is: “Produksjon og salg av møbler.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK −19,000
Equity
NOK −573,000

Financial health · 2024

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-150.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GJESDAL MØBEL AS?

HARRY KENNETH HELLAND
GJESDAL MØBEL AS
NOK 46,000 rev. · NOK −19,000 profit

GJESDAL MØBEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GJESDAL MØBEL AS

Who owns GJESDAL MØBEL AS?

HARRY KENNETH HELLAND is the largest registered owner, with 100.0%.

What is the revenue of GJESDAL MØBEL AS?

GJESDAL MØBEL AS had revenue of NOK 46,000 in 2024.

Who is the general manager of GJESDAL MØBEL AS?

Harry Kenneth Helland is registered as general manager of GJESDAL MØBEL AS.

Where is GJESDAL MØBEL AS based?

GJESDAL MØBEL AS has its business address in Ålgård.

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.