BIZTRAC BETA
Construction of residential and non-residential buildings

ROZENBERG BYGG AS

Org. no. 935497515 Limited company (AS) Samnanger Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 566,000
Equity NOK 430,000
Incorporated 2025
Share capital NOK 30,000

ROZENBERG BYGG AS is registered as a limited company in Samnanger, Vestland with organisation number 935497515. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen oppføring av bygninger - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 566,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
Operating profit
NOK 566,000
Equity
NOK 430,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns ROZENBERG BYGG AS?

JANIS ROZENBERGS
ROZENBERG BYGG AS
NOK 4.9m rev. · NOK 566,000 profit

ROZENBERG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROZENBERG BYGG AS

Who owns ROZENBERG BYGG AS?

JANIS ROZENBERGS is the largest registered owner, with 100.0%.

What is the revenue of ROZENBERG BYGG AS?

ROZENBERG BYGG AS had revenue of NOK 4.9m in 2025.

Who is the general manager of ROZENBERG BYGG AS?

Janis Rozenbergs is registered as general manager of ROZENBERG BYGG AS.

Where is ROZENBERG BYGG AS based?

ROZENBERG BYGG AS has its business address in Tysse.

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.