BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

JESSEN UNITED AS

Org. no. 927026317 Limited company (AS) Vefsn Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 430,000
Operating profit NOK 203,000
Equity NOK 467,000
Incorporated 2021
Share capital NOK 30,000

JESSEN UNITED AS is registered as a limited company in Vefsn, Nordland with organisation number 927026317. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester. Utleie av hus, hytter og annet i tilknytning til dette. Selskapet skal også drive kjøp og salg av aksjer o.l.”. The most recent filed accounts, for the 2025 financial year, show NOK 430,000 in revenue and NOK 203,000 in operating profit.

Key figures · 2025

Revenue
NOK 430,000
Operating profit
NOK 203,000
Equity
NOK 467,000
Est. value
NOK 950,000

Financial health · 2025

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

Who owns JESSEN UNITED AS?

KURT JESSEN JOHANSSON
JESSEN UNITED AS
NOK 430,000 rev. · NOK 203,000 profit

JESSEN UNITED AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JESSEN UNITED AS own?

JESSEN UNITED AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JESSEN UNITED AS

Who owns JESSEN UNITED AS?

KURT JESSEN JOHANSSON is the largest registered owner, with 100.0%.

What is the revenue of JESSEN UNITED AS?

JESSEN UNITED AS had revenue of NOK 430,000 in 2025.

Where is JESSEN UNITED AS based?

JESSEN UNITED 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.