BIZTRAC BETA
Freight ocean transport

BARENTS MARITIME AS

Org. no. 914589126 Limited company (AS) Harstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 503,000
Equity NOK 6.7m
Incorporated 2014
Share capital NOK 30,000

BARENTS MARITIME AS is registered as a limited company in Harstad, Troms with organisation number 914589126. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rederivirksomhet med eller uten selveid fartøy. Management av fiske- og fraktefartøyer. Konsulentvirksomhet for fiske- og fraktefartøyer og for oppdrettsnæringen. Skal kunne gå inn som eiere i andre beslektede selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 503,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 503,000
Equity
NOK 6.7m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns BARENTS MARITIME AS?

ERLEND KRISTIANSEN
BARENTS MARITIME AS
NOK 1.0m rev. · NOK 503,000 profit

BARENTS MARITIME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARENTS MARITIME AS

Who owns BARENTS MARITIME AS?

ERLEND KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of BARENTS MARITIME AS?

BARENTS MARITIME AS had revenue of NOK 1.0m in 2025.

Who is the general manager of BARENTS MARITIME AS?

Erlend Kristiansen is registered as general manager of BARENTS MARITIME AS.

Where is BARENTS MARITIME AS based?

BARENTS MARITIME AS has its business address in Harstad.

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.