BIZTRAC BETA
Repair and maintenance of machinery

JONSTEN AS

Org. no. 914858550 Limited company (AS) Råde Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 111,000
Operating profit NOK −8,000
Equity NOK 137,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

JONSTEN AS is registered as a limited company in Råde, Østfold with organisation number 914858550. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie, kjøp og salg av maskiner og utstyr. Entreprenørvirksomhet, rep og vedlikehold herunder verkstedvirksomhet. Import og eksport av varer og utstyr. Kjøp og salg av verdipapirer, og ellers det som naturlig faller innenfor virksomheten.”. The most recent filed accounts, for the 2025 financial year, show NOK 111,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 111,000
Operating profit
NOK −8,000
Equity
NOK 137,000
Est. value
NOK 129,000

Financial health · 2025

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

Who owns JONSTEN AS?

ØRJAN HAUGESTEN
JONSTEN AS
NOK 111,000 rev. · NOK −8,000 profit

JONSTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JONSTEN AS

Who owns JONSTEN AS?

ØRJAN HAUGESTEN is the largest registered owner, with 100.0%.

What is the revenue of JONSTEN AS?

JONSTEN AS had revenue of NOK 111,000 in 2025.

Who is the general manager of JONSTEN AS?

Per Haugesten is registered as general manager of JONSTEN AS.

Where is JONSTEN AS based?

JONSTEN AS has its business address in Råde.

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.