BIZTRAC BETA
Repair and maintenance of civilian ships and boats

ESPOMAR SERVICES AS

Org. no. 986720936 Limited company (AS) Kragerø Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 1.8m
Equity NOK 1.8m
Incorporated 2004
Share capital NOK 100,000

ESPOMAR SERVICES AS is registered as a limited company in Kragerø, Telemark with organisation number 986720936. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av tjenester innen elektronikk, automasjon og elektro til skip, samt dertil hørende tjenester. Selskapet skal også ha anledning til å delta og eie aksjer i tilsvarende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 1.8m
Equity
NOK 1.8m
Est. value
NOK 6.6m

Financial health · 2025

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

Who owns ESPOMAR SERVICES AS?

JØRN ESPOLIN JOHNSON
ESPOMAR SERVICES AS
NOK 3.3m rev. · NOK 1.8m profit

ESPOMAR SERVICES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESPOMAR SERVICES AS

Who owns ESPOMAR SERVICES AS?

JØRN ESPOLIN JOHNSON is the largest registered owner, with 100.0%.

What is the revenue of ESPOMAR SERVICES AS?

ESPOMAR SERVICES AS had revenue of NOK 3.3m in 2025.

Who is the general manager of ESPOMAR SERVICES AS?

Jørn Espolin Johnson is registered as general manager of ESPOMAR SERVICES AS.

Where is ESPOMAR SERVICES AS based?

ESPOMAR SERVICES AS has its business address in Kragerø.

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.