biztrac. BETA
COMPANY REGISTER PROFILE
913108337 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Painting and glazing

RAD-BYGG AS

Org. no. 913108337 Limited company (AS) Oslo Incorporated 2014 Active
Revenue 2025 NOK 29.1m
Operating profit NOK 3.1m
Equity NOK 321,000
Incorporated 2014
Employees 19
Share capital NOK 30,000

RAD-BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 913108337. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2014 and has 19 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Håndverkstjenester: Maling, bygging, flislegging og andre vedlikeholdstjenester, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.1m in revenue and NOK 3.1m in operating profit.

Key figures · 2025

Revenue
NOK 29.1m
▲ +2 %
Operating profit
NOK 3.1m
▲ +46 %
Equity
NOK 321,000
▲ +311 %
Est. value
NOK 8.7m

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
42.5%
Very good
Return on total assets
Solidity
4.1%
Weak
Equity as a share of total capital

Who owns RAD-BYGG AS?

RAD-BYGG AS
NOK 29.1m rev. · NOK 3.1m profit

RAD-BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAD-BYGG AS

Who owns RAD-BYGG AS?

Radoslaw Chmielewski is the largest registered owner, with 100.0%.

What is the revenue of RAD-BYGG AS?

RAD-BYGG AS had revenue of NOK 29.1m in 2025.

Who is the general manager of RAD-BYGG AS?

Radoslaw Chmielewski is registered as general manager of RAD-BYGG AS.

Where is RAD-BYGG AS based?

RAD-BYGG AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.