biztrac. BETA
COMPANY REGISTER PROFILE
915792189 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

FLISNES NÆRINGSBYGG AS

Org. no. 915792189 Limited company (AS) Sula Incorporated 2015 Active
Revenue 2025 NOK 12.2m
Operating profit NOK 10.2m
Equity NOK 68.3m
Incorporated 2015
Share capital NOK 10.0m

FLISNES NÆRINGSBYGG AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 915792189. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Å eie og forvalte fast eiendom, herunder bygge ut og leie ut, av samt alt som står i forbindelse med detter, herunder deltakelse i andre selskaper og lignende virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.2m in revenue and NOK 10.2m in operating profit.

Key figures · 2025

Revenue
NOK 12.2m
▲ +2 %
Operating profit
NOK 10.2m
▲ +3 %
Equity
NOK 68.3m
▲ +12 %
Est. value
NOK 70.5m

Financial health · 2025

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
13.3%
Good
Return on total assets
Solidity
88.3%
Very good
Equity as a share of total capital

Who owns FLISNES NÆRINGSBYGG AS?

FLISNES NÆRINGSBYGG AS has 3 registered shareholders:

All shareholders and roles →

Group structure

FLISNES NÆRINGSBYGG AS er morselskap for 33 datterselskaper:

Frequently asked questions about FLISNES NÆRINGSBYGG AS

Who owns FLISNES NÆRINGSBYGG AS?

H.I. GIØRTZ HOLDING AS is the largest registered owner, with 65.0%.

What is the revenue of FLISNES NÆRINGSBYGG AS?

FLISNES NÆRINGSBYGG AS had revenue of NOK 12.2m in 2025.

Where is FLISNES NÆRINGSBYGG AS based?

FLISNES NÆRINGSBYGG AS has its business address in Eidsnes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.