biztrac. BETA
COMPANY REGISTER PROFILE
812038842 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of metal structures and parts of structures

MARIN RØR AS

Org. no. 812038842 Limited company (AS) Fredrikstad Incorporated 2013 Active
Revenue 2025 NOK 20.1m
Operating profit NOK 817,000
Equity NOK 5.0m
Incorporated 2013
Employees 16
Share capital NOK 30,000

MARIN RØR AS is registered as a limited company in Fredrikstad, Østfold with organisation number 812038842. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 2013 and has 16 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Industrirørlegging og sveising.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.1m in revenue and NOK 817,000 in operating profit.

Former names: PKM DRIFT AS

Key figures · 2025

Revenue
NOK 20.1m
▲ +9 %
Operating profit
NOK 817,000
▲ +373 %
Equity
NOK 5.0m
▲ +16 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
2.00
Very good
Current assets ÷ current liabilities
Profitability
10.8%
Good
Return on total assets
Solidity
59.0%
Very good
Equity as a share of total capital

Who owns MARIN RØR AS?

MARIN RØR AS
NOK 20.1m rev. · NOK 817,000 profit

MARIN RØR AS has 2 registered shareholders:

All shareholders and roles →

Group structure

MARIN RØR AS er morselskap for 3 datterselskaper:

Frequently asked questions about MARIN RØR AS

Who owns MARIN RØR AS?

THERMA INDUSTRI AS is the largest registered owner, with 80.0%.

What is the revenue of MARIN RØR AS?

MARIN RØR AS had revenue of NOK 20.1m in 2025.

Who is the general manager of MARIN RØR AS?

Ivar Laurits Johansen is registered as general manager of MARIN RØR AS.

Where is MARIN RØR AS based?

MARIN RØR AS has its business address in Rolvsøy.

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.