BIZTRAC BETA
Rental and operating of own or leased real estate

FUGLESKJÆRET NÆRINGSBYGG AS

Org. no. 898271382 Limited company (AS) Kinn Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 2.0m
Equity NOK 6.5m
Incorporated 2011
Share capital NOK 104,000

FUGLESKJÆRET NÆRINGSBYGG AS is registered as a limited company in Kinn, Vestland with organisation number 898271382. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 104,000, divided into 10400 shares. The company's stated purpose is: “Investering, utvikling, salg og utleie av eiendom, samt virksomhet som står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 2.0m
Equity
NOK 6.5m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns FUGLESKJÆRET NÆRINGSBYGG AS?

MIMAR HOLDING AS
FUGLESKJÆRET NÆRINGSBYGG AS
NOK 4.4m rev. · NOK 2.0m profit

FUGLESKJÆRET NÆRINGSBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FUGLESKJÆRET NÆRINGSBYGG AS

Who owns FUGLESKJÆRET NÆRINGSBYGG AS?

MIMAR HOLDING AS is the largest registered owner, with 75.0%.

What is the revenue of FUGLESKJÆRET NÆRINGSBYGG AS?

FUGLESKJÆRET NÆRINGSBYGG AS had revenue of NOK 4.4m in 2024.

Who is the general manager of FUGLESKJÆRET NÆRINGSBYGG AS?

John Sigurd Solberg is registered as general manager of FUGLESKJÆRET NÆRINGSBYGG AS.

Where is FUGLESKJÆRET NÆRINGSBYGG AS based?

FUGLESKJÆRET NÆRINGSBYGG AS has its business address in Florø.

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.