BIZTRAC BETA
Other specialised construction activities n.e.c.

BMF DRIFT AS

Org. no. 927239620 Limited company (AS) Karmøy Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 140,000
Operating profit NOK 28,000
Equity NOK 41,000
Incorporated 2021
Share capital NOK 30,000

BMF DRIFT AS is registered as a limited company in Karmøy, Rogaland with organisation number 927239620. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Betongarbeid og murerarbeid. Malertjenester og stillas. Utleie av maskiner og arbeidskraft. Kjøp og videresalg av tjenester og materiell og alt tilhørende og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 140,000 in revenue and NOK 28,000 in operating profit.

Key figures · 2024

Revenue
NOK 140,000
Operating profit
NOK 28,000
Equity
NOK 41,000
Est. value
NOK 104,000

Financial health · 2023

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

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

Who owns BMF DRIFT AS?

YLIME HOLDING AS
BMF DRIFT AS
NOK 140,000 rev. · NOK 28,000 profit

BMF DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BMF DRIFT AS

Who owns BMF DRIFT AS?

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

What is the revenue of BMF DRIFT AS?

BMF DRIFT AS had revenue of NOK 140,000 in 2024.

Who is the general manager of BMF DRIFT AS?

Rasmus Ferkingstad is registered as general manager of BMF DRIFT AS.

Where is BMF DRIFT AS based?

BMF DRIFT AS has its business address in Skudeneshavn.

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.