BIZTRAC BETA
Roofing activities

RD BLIKK OG VENTILASJON AS

Org. no. 976098331 Limited company (AS) Trondheim Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 15.0m
Operating profit NOK 612,000
Equity NOK 3.3m
Incorporated 1996
Employees 10
Share capital NOK 104,000

RD BLIKK OG VENTILASJON AS is registered as a limited company in Trondheim, Trøndelag with organisation number 976098331. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1996 and has 10 registered employees. Registered share capital is NOK 104,000, divided into 52 shares. The company's stated purpose is: “Salg av blikkenslagertjenester og relaterte produkter. Selskapet skal også kunne delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.0m in revenue and NOK 612,000 in operating profit.

Key figures · 2024

Revenue
NOK 15.0m
Operating profit
NOK 612,000
Equity
NOK 3.3m
Est. value
NOK 3.6m

Financial health · 2024

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

Who owns RD BLIKK OG VENTILASJON AS?

TRIPOLIS EIENDOM AS
RD BLIKK OG VENTILASJON AS
NOK 15.0m rev. · NOK 612,000 profit

RD BLIKK OG VENTILASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RD BLIKK OG VENTILASJON AS

Who owns RD BLIKK OG VENTILASJON AS?

TRIPOLIS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of RD BLIKK OG VENTILASJON AS?

RD BLIKK OG VENTILASJON AS had revenue of NOK 15.0m in 2024.

Who is the general manager of RD BLIKK OG VENTILASJON AS?

Roger Dahlberg is registered as general manager of RD BLIKK OG VENTILASJON AS.

Where is RD BLIKK OG VENTILASJON AS based?

RD BLIKK OG VENTILASJON AS has its business address in Trondheim.

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.