BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGFORNYING AS

Org. no. 920274188 Limited company (AS) Sandnes Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 190.1m
Operating profit NOK 9.1m
Equity NOK 24.3m
Incorporated 2018
Employees 13
Share capital NOK 1.0m

BYGGFORNYING AS is registered as a limited company in Sandnes, Rogaland with organisation number 920274188. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 13 registered employees. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Å levere tjenester av enhver art knyttet til modernisering/ rehabilitering av næringsbygg, samt alt som står i naturlig forbindelse med dette, herunder å delta i selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 190.1m in revenue and NOK 9.1m in operating profit.

Key figures · 2025

Revenue
NOK 190.1m
Operating profit
NOK 9.1m
Equity
NOK 24.3m
Est. value
NOK 42.3m

Financial health · 2025

Liquidity
1.68
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.9%
Very good
Equity as a share of total capital

Who owns BYGGFORNYING AS?

BIRKEN & CO AS
BYGGFORNYING AS
NOK 190.1m rev. · NOK 9.1m profit

BYGGFORNYING AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGFORNYING AS

Who owns BYGGFORNYING AS?

BIRKEN & CO AS is the largest registered owner, with 52.0%.

What is the revenue of BYGGFORNYING AS?

BYGGFORNYING AS had revenue of NOK 190.1m in 2025.

Who is the general manager of BYGGFORNYING AS?

Ole Martin Vedøy is registered as general manager of BYGGFORNYING AS.

Where is BYGGFORNYING AS based?

BYGGFORNYING AS has its business address in Sandnes.

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.