BIZTRAC BETA
COMPANY REGISTER PROFILE
994251848 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Manufacture of metal structures and parts of structures

RØRA MEK VERKSTED AS

Org. no. 994251848 Limited company (AS) Inderøy Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 224,000
Equity NOK 33,000
Incorporated 2009
Share capital NOK 333,000

RØRA MEK VERKSTED AS is registered as a limited company in Inderøy, Trøndelag with organisation number 994251848. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 2009. Registered share capital is NOK 333,000, divided into 666668 shares. The company's stated purpose is: “Drive smie og mekanisk verksted.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 224,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
▼ −36 %
Operating profit
NOK 224,000
▲ +116 %
Equity
NOK 33,000
▲ +104 %
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
8.0%
Satisfactory
Return on total assets
Solidity
1.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RØRA MEK VERKSTED AS?

RØRA MEK VERKSTED AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØRA MEK VERKSTED AS

Who owns RØRA MEK VERKSTED AS?

NESS-VANGSTAD HOLDING AS is the largest registered owner, with 55.0%.

What is the revenue of RØRA MEK VERKSTED AS?

RØRA MEK VERKSTED AS had revenue of NOK 6.2m in 2025.

Who is the general manager of RØRA MEK VERKSTED AS?

Katarzyna Joanna Lozinska is registered as general manager of RØRA MEK VERKSTED AS.

Where is RØRA MEK VERKSTED AS based?

RØRA MEK VERKSTED AS has its business address in Inderøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.