BIZTRAC BETA
Freight coastal transport

EMILSEN REDERI AS

Org. no. 916595085 Limited company (AS) Nærøysund Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 24.8m
Operating profit NOK 5.6m
Equity NOK 24.6m
Incorporated 2015
Employees 10
Share capital NOK 30,000

EMILSEN REDERI AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 916595085. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2015 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive sjøveis transportvirksomhet herunder serviceoppdrag gjennom egne eller innleide skip til oppdrettsnæringen.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.8m in revenue and NOK 5.6m in operating profit.

Key figures · 2024

Revenue
NOK 24.8m
Operating profit
NOK 5.6m
Equity
NOK 24.6m
Est. value
NOK 29.6m

Financial health · 2024

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

Who owns EMILSEN REDERI AS?

EMILSEN SJØSERVICE AS
EMILSEN REDERI AS
NOK 24.8m rev. · NOK 5.6m profit

EMILSEN REDERI AS has 1 registered shareholder:

All shareholders and roles →

Group structure

EMILSEN REDERI AS er morselskap for 18 datterselskaper:

Frequently asked questions about EMILSEN REDERI AS

Who owns EMILSEN REDERI AS?

EMILSEN SJØSERVICE AS is the largest registered owner, with 100.0%.

What is the revenue of EMILSEN REDERI AS?

EMILSEN REDERI AS had revenue of NOK 24.8m in 2024.

Who is the general manager of EMILSEN REDERI AS?

Ila Yvonne Emilsen is registered as general manager of EMILSEN REDERI AS.

Where is EMILSEN REDERI AS based?

EMILSEN REDERI AS has its business address in Rørvik.

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.