BIZTRAC BETA
Development of building projects

ROSSELAND BYGG AS

Org. no. 913106652 Limited company (AS) Sola Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 142,000
Equity NOK 315,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ROSSELAND BYGG AS is registered as a limited company in Sola, Rogaland with organisation number 913106652. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Entreprenørvirksomhet og alt som står i forbindelse med dette, samt herunder handelsvirksomhet, import og eksport samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 142,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 142,000
Equity
NOK 315,000
Est. value
NOK 563,000

Financial health · 2025

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

Who owns ROSSELAND BYGG AS?

HEXON HOLDING AS
ROSSELAND BYGG AS
NOK 2.6m rev. · NOK 142,000 profit

ROSSELAND BYGG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ROSSELAND BYGG AS er morselskap for 8 datterselskaper:

Frequently asked questions about ROSSELAND BYGG AS

Who owns ROSSELAND BYGG AS?

HEXON HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ROSSELAND BYGG AS?

ROSSELAND BYGG AS had revenue of NOK 2.6m in 2025.

Where is ROSSELAND BYGG AS based?

ROSSELAND BYGG AS has its business address in Sola.

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.