BIZTRAC BETA
Site preparation

FLEVIG MASKIN AS

Org. no. 934670000 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 376,000
Operating profit NOK −11,000
Equity NOK 90,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

FLEVIG MASKIN AS is registered as a limited company in Stavanger, Rogaland with organisation number 934670000. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Entreprenørvirksomhet innen grunnarbeid samt annet som kan forbindes med dette samt deltagelse og investering i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 376,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 376,000
Operating profit
NOK −11,000
Equity
NOK 90,000
Est. value
NOK 165,000

Financial health · 2025

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

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

Who owns FLEVIG MASKIN AS?

FLEVIG HOLDING AS
FLEVIG MASKIN AS
NOK 376,000 rev. · NOK −11,000 profit

FLEVIG MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLEVIG MASKIN AS

Who owns FLEVIG MASKIN AS?

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

What is the revenue of FLEVIG MASKIN AS?

FLEVIG MASKIN AS had revenue of NOK 376,000 in 2025.

Who is the general manager of FLEVIG MASKIN AS?

Jan Håvard Flesjå is registered as general manager of FLEVIG MASKIN AS.

Where is FLEVIG MASKIN AS based?

FLEVIG MASKIN AS has its business address in Finnøy.

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.