BIZTRAC BETA
Wholesale of clothing and footwear

JOBBUTSTYR AS

Org. no. 823160712 Limited company (AS) Kinn Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 638,000
Operating profit NOK 212,000
Equity NOK −115,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−115k kr).

JOBBUTSTYR AS is registered as a limited company in Kinn, Vestland with organisation number 823160712. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge kvalitetsprodukter innen personlig verneutstyr og vernesko til bedrifter og privatpersoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 638,000 in revenue and NOK 212,000 in operating profit.

Key figures · 2024

Revenue
NOK 638,000
Operating profit
NOK 212,000
Equity
NOK −115,000
Est. value
NOK 1.1m

Financial health · 2024

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

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

Who owns JOBBUTSTYR AS?

HANSEN HAUKÅS HOLDING AS
JOBBUTSTYR AS
NOK 638,000 rev. · NOK 212,000 profit

JOBBUTSTYR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JOBBUTSTYR AS

Who owns JOBBUTSTYR AS?

HANSEN HAUKÅS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of JOBBUTSTYR AS?

JOBBUTSTYR AS had revenue of NOK 638,000 in 2024.

Who is the general manager of JOBBUTSTYR AS?

Lennarth Hansen Haukås is registered as general manager of JOBBUTSTYR AS.

Where is JOBBUTSTYR AS based?

JOBBUTSTYR AS has its business address in Florø.

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.