biztrac. BETA
COMPANY REGISTER PROFILE
996650049 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other support activities for petroleum and natural gas extraction

REM SALTIRE AS

Org. no. 996650049 Limited company (AS) Herøy Incorporated 2011 Active
Revenue 2025 NOK 146.9m
Operating profit NOK 107.0m
Equity NOK 193.3m
Incorporated 2011
Share capital NOK 21.0m

REM SALTIRE AS is registered as a limited company in Herøy, Møre og Romsdal with organisation number 996650049. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2011. Registered share capital is NOK 21.0m, divided into 2100 shares. The company's stated purpose is: “Å drive rederivirksomhet samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 146.9m in revenue and NOK 107.0m in operating profit.

Former names: BJØRNEN 2 AS, E FORLAND AS

Key figures · 2025

Revenue
NOK 146.9m
▼ −30 %
Operating profit
NOK 107.0m
▼ −23 %
Equity
NOK 193.3m
▼ −11 %
Est. value
NOK 344.0m

Financial health · 2025

Liquidity
4.52
Very good
Current assets ÷ current liabilities
Profitability
27.9%
Very good
Return on total assets
Solidity
48.0%
Very good
Equity as a share of total capital

Who owns REM SALTIRE AS?

REM SALTIRE AS
NOK 146.9m rev. · NOK 107.0m profit

REM SALTIRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REM SALTIRE AS

Who owns REM SALTIRE AS?

REM SALTIRE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of REM SALTIRE AS?

REM SALTIRE AS had revenue of NOK 146.9m in 2025.

Who is the general manager of REM SALTIRE AS?

Lars Oddvar Conradi Andersen is registered as general manager of REM SALTIRE AS.

Where is REM SALTIRE AS based?

REM SALTIRE AS has its business address in Fosnavåg.

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.