BIZTRAC BETA
Construction of residential and non-residential buildings

FRONT BYGG ROGALAND AS

Org. no. 925702498 Limited company (AS) Sandnes Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 56.8m
Operating profit NOK 4.4m
Equity NOK 11.2m
Incorporated 2020
Employees 22
Share capital NOK 2.5m

FRONT BYGG ROGALAND AS is registered as a limited company in Sandnes, Rogaland with organisation number 925702498. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020 and has 22 registered employees. Registered share capital is NOK 2.5m, divided into 30000 shares. The company's stated purpose is: “Byggevirksomhet samt hva dermed står i forbindelse, herunder delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 56.8m in revenue and NOK 4.4m in operating profit.

Key figures · 2025

Revenue
NOK 56.8m
Operating profit
NOK 4.4m
Equity
NOK 11.2m
Est. value
NOK 20.7m

Financial health · 2025

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

Who owns FRONT BYGG ROGALAND AS?

SASAM AS
FRONT BYGG ROGALAND AS
NOK 56.8m rev. · NOK 4.4m profit

FRONT BYGG ROGALAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRONT BYGG ROGALAND AS

Who owns FRONT BYGG ROGALAND AS?

SASAM AS is the largest registered owner, with 100.0%.

What is the revenue of FRONT BYGG ROGALAND AS?

FRONT BYGG ROGALAND AS had revenue of NOK 56.8m in 2025.

Who is the general manager of FRONT BYGG ROGALAND AS?

Aadne Meling is registered as general manager of FRONT BYGG ROGALAND AS.

Where is FRONT BYGG ROGALAND AS based?

FRONT BYGG ROGALAND 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.