BIZTRAC BETA
Manufacture of metal structures and parts of structures

REMEK AS

Org. no. 959325928 Limited company (AS) Karmøy Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 18.4m
Operating profit NOK 5.2m
Equity NOK 13.6m
Incorporated 1990
Employees 8
Share capital NOK 202,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

REMEK AS is registered as a limited company in Karmøy, Rogaland with organisation number 959325928. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 1990 and has 8 registered employees. Registered share capital is NOK 202,000, divided into 184 shares. The company's stated purpose is: “Mekanisk verksted med tilhørende produksjon samt hva hermed står i forbindelse, herunder å delta i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.4m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 18.4m
Operating profit
NOK 5.2m
Equity
NOK 13.6m
Est. value
NOK 24.4m

Financial health · 2024

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

Who owns REMEK AS?

SMED AS
REMEK AS
NOK 18.4m rev. · NOK 5.2m profit

REMEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REMEK AS

Who owns REMEK AS?

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

What is the revenue of REMEK AS?

REMEK AS had revenue of NOK 18.4m in 2024.

Who is the general manager of REMEK AS?

Torgeir Strøm is registered as general manager of REMEK AS.

Where is REMEK AS based?

REMEK AS has its business address in Kopervik.

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.