BIZTRAC BETA
Manufacture of other general-purpose machinery n.e.c.

M.F.E. FIRE PROTECTION AS

Org. no. 924506636 Limited company (AS) Sunnfjord Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 90,000
Operating profit NOK 69,000
Equity NOK 409,000
Incorporated 2020
Share capital NOK 200,000

M.F.E. FIRE PROTECTION AS is registered as a limited company in Sunnfjord, Vestland with organisation number 924506636. The business is classified under manufacture of other general-purpose machinery n.e.c. (NACE 28.290). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av slokkeløsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 90,000 in revenue and NOK 69,000 in operating profit.

Key figures · 2025

Revenue
NOK 90,000
Operating profit
NOK 69,000
Equity
NOK 409,000
Est. value
NOK 428,000

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.7%
Weak
Equity as a share of total capital

Who owns M.F.E. FIRE PROTECTION AS?

MI-HOLDING AS
M.F.E. FIRE PROTECTION AS
NOK 90,000 rev. · NOK 69,000 profit

M.F.E. FIRE PROTECTION AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about M.F.E. FIRE PROTECTION AS

Who owns M.F.E. FIRE PROTECTION AS?

MI-HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of M.F.E. FIRE PROTECTION AS?

M.F.E. FIRE PROTECTION AS had revenue of NOK 90,000 in 2025.

Who is the general manager of M.F.E. FIRE PROTECTION AS?

Morten Falkenstein Engebø is registered as general manager of M.F.E. FIRE PROTECTION AS.

Where is M.F.E. FIRE PROTECTION AS based?

M.F.E. FIRE PROTECTION AS has its business address in Førde.

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.