BIZTRAC BETA
Repair and maintenance of machinery

RM MASKIN & VERKSTEDSDRIFT AS

Org. no. 920482767 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 323,000
Equity NOK 3.9m
Incorporated 2018
Share capital NOK 30,000

RM MASKIN & VERKSTEDSDRIFT AS is registered as a limited company in Bergen, Vestland with organisation number 920482767. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Reparasjon av maskiner. Utleie av maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 323,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 323,000
Equity
NOK 3.9m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns RM MASKIN & VERKSTEDSDRIFT AS?

RUDI ALEXANDER MARTHINSSON
RM MASKIN & VERKSTEDSDRIFT AS
NOK 1.3m rev. · NOK 323,000 profit

RM MASKIN & VERKSTEDSDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RM MASKIN & VERKSTEDSDRIFT AS

Who owns RM MASKIN & VERKSTEDSDRIFT AS?

RUDI ALEXANDER MARTHINSSON is the largest registered owner, with 90.0%.

What is the revenue of RM MASKIN & VERKSTEDSDRIFT AS?

RM MASKIN & VERKSTEDSDRIFT AS had revenue of NOK 1.3m in 2025.

Who is the general manager of RM MASKIN & VERKSTEDSDRIFT AS?

Rudi Alexander Marthinsson is registered as general manager of RM MASKIN & VERKSTEDSDRIFT AS.

Where is RM MASKIN & VERKSTEDSDRIFT AS based?

RM MASKIN & VERKSTEDSDRIFT AS has its business address in Haukeland.

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.