biztrac. BETA
COMPANY REGISTER PROFILE
928337936 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Freight ocean transport

PELAGIA SJØ AS

Org. no. 928337936 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 125.6m
Operating profit NOK 5.1m
Equity NOK 10.9m
Incorporated 2021
Employees 113
Share capital NOK 100,000

PELAGIA SJØ AS is registered as a limited company in Bergen, Vestland with organisation number 928337936. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2021 and has 113 registered employees. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Drive med utleie av arbeidskraft innenfor sjøfart og shipping, drift av skip og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 125.6m in revenue and NOK 5.1m in operating profit.

Former names: HORDAFOR II AS, HORDAFOR AS

Key figures · 2025

Revenue
NOK 125.6m
▲ +24 %
Operating profit
NOK 5.1m
▲ +22 %
Equity
NOK 10.9m
▲ +0 %
Est. value
NOK 18.5m

Financial health · 2025

Liquidity
1.08
Satisfactory
Current assets ÷ current liabilities
Profitability
4.0%
Weak
Return on total assets
Solidity
7.8%
Weak
Equity as a share of total capital

Who owns PELAGIA SJØ AS?

PELAGIA SJØ AS
NOK 125.6m rev. · NOK 5.1m profit

PELAGIA SJØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PELAGIA SJØ AS

Who owns PELAGIA SJØ AS?

PELAGIA AS is the largest registered owner, with 100.0%.

What is the revenue of PELAGIA SJØ AS?

PELAGIA SJØ AS had revenue of NOK 125.6m in 2025.

Who is the general manager of PELAGIA SJØ AS?

Nils Andre Hille is registered as general manager of PELAGIA SJØ AS.

Where is PELAGIA SJØ AS based?

PELAGIA SJØ AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.