BIZTRAC BETA
Construction of residential and non-residential buildings

FINNØY BYGG AS

Org. no. 995641224 Limited company (AS) Stavanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 7.2m
Operating profit NOK 237,000
Equity NOK 1.5m
Incorporated 2010
Employees 9
Share capital NOK 107,000

FINNØY BYGG AS is registered as a limited company in Stavanger, Rogaland with organisation number 995641224. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2010 and has 9 registered employees. Registered share capital is NOK 107,000, divided into 107 shares. The company's stated purpose is: “Salg av varer og tjenester, samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.2m in revenue and NOK 237,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.2m
Operating profit
NOK 237,000
Equity
NOK 1.5m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.8%
Good
Equity as a share of total capital

Who owns FINNØY BYGG AS?

FINNØY BYGG AS
FINNØY BYGG AS
NOK 7.2m rev. · NOK 237,000 profit

FINNØY BYGG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FINNØY BYGG AS own?

FINNØY BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FINNØY BYGG AS

Who owns FINNØY BYGG AS?

FINNØY BYGG AS is the largest registered owner, with 50.5%.

What is the revenue of FINNØY BYGG AS?

FINNØY BYGG AS had revenue of NOK 7.2m in 2025.

Who is the general manager of FINNØY BYGG AS?

Tom Erik Risa is registered as general manager of FINNØY BYGG AS.

Where is FINNØY BYGG AS based?

FINNØY BYGG AS has its business address in Rennesø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.