BIZTRAC BETA
Construction of residential and non-residential buildings

FLUGRE BYGG AS

Org. no. 915080324 Limited company (AS) Sykkylven Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 788
Equity NOK −75,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−75k kr).

FLUGRE BYGG AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 915080324. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oppføring av bygg og rehabilitering, samt annet som naturlig er knyttet til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 788 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 788
Equity
NOK −75,000
Est. value
NOK 5,000

Financial health · 2025

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-38.1%
Weak
Equity as a share of total capital

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

Who owns FLUGRE BYGG AS?

ØYVIND FLUGRE
FLUGRE BYGG AS
NOK 1.1m rev. · NOK 788 profit

FLUGRE BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLUGRE BYGG AS

Who owns FLUGRE BYGG AS?

ØYVIND FLUGRE is the largest registered owner, with 100.0%.

What is the revenue of FLUGRE BYGG AS?

FLUGRE BYGG AS had revenue of NOK 1.1m in 2025.

Who is the general manager of FLUGRE BYGG AS?

Øyvind Flugre is registered as general manager of FLUGRE BYGG AS.

Where is FLUGRE BYGG AS based?

FLUGRE BYGG AS has its business address in Sykkylven.

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.