BIZTRAC BETA
Painting and glazing

J EBERG HANSEN AS

Org. no. 935991420 Limited company (AS) Vefsn Incorporated 1984 Active
Ownership graph ↗
Revenue 2024 NOK 21.9m
Operating profit NOK −1.2m
Equity NOK 274,000
Incorporated 1984
Employees 14
Share capital NOK 1.8m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

J EBERG HANSEN AS is registered as a limited company in Vefsn, Nordland with organisation number 935991420. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 1984 and has 14 registered employees. Registered share capital is NOK 1.8m, divided into 750 shares. The company's stated purpose is: “Drive salg og produksjon av bygningsglass, alumin- iumskonstruksjoner og bygningsartikler ellers og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.9m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 21.9m
Operating profit
NOK −1.2m
Equity
NOK 274,000
Est. value
NOK 6.0m

Financial health · 2024

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.4%
Not satisfactory
Equity as a share of total capital

Who owns J EBERG HANSEN AS?

PJH HOLDING AS
J EBERG HANSEN AS
NOK 21.9m rev. · NOK −1.2m profit

J EBERG HANSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J EBERG HANSEN AS

Who owns J EBERG HANSEN AS?

PJH HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of J EBERG HANSEN AS?

J EBERG HANSEN AS had revenue of NOK 21.9m in 2024.

Who is the general manager of J EBERG HANSEN AS?

Per-Jakob Hansen is registered as general manager of J EBERG HANSEN AS.

Where is J EBERG HANSEN AS based?

J EBERG HANSEN AS has its business address in Mosjøen.

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.