BIZTRAC BETA
Roofing activities

RINGERIKE BLIKK OG TAK AS

Org. no. 935834023 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 9.9m
Operating profit NOK 2.2m
Equity NOK 906,000
Incorporated 2025
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

RINGERIKE BLIKK OG TAK AS is registered as a limited company in Ringerike, Buskerud with organisation number 935834023. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2025 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Blikkenslagervirksomhet, handel og hva som står i forbindelse, samt eie og investere i aksjer og det som står i naturlig forbindelse med dette.”.

Key figures

Revenue
NOK 9.9m
Operating profit
NOK 2.2m
Equity
NOK 906,000
Est. value
NOK 6.5m

Financial health · 2025

Liquidity
2.52
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.7%
Satisfactory
Equity as a share of total capital

Who owns RINGERIKE BLIKK OG TAK AS?

RINGERIKE B&T HOLDING AS
RINGERIKE BLIKK OG TAK AS
NOK 9.9m rev. · NOK 2.2m profit

RINGERIKE BLIKK OG TAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RINGERIKE BLIKK OG TAK AS

Who owns RINGERIKE BLIKK OG TAK AS?

RINGERIKE B&T HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RINGERIKE BLIKK OG TAK AS?

RINGERIKE BLIKK OG TAK AS had revenue of NOK 9.9m.

Who is the general manager of RINGERIKE BLIKK OG TAK AS?

Tom Løhre is registered as general manager of RINGERIKE BLIKK OG TAK AS.

Where is RINGERIKE BLIKK OG TAK AS based?

RINGERIKE BLIKK OG TAK AS has its business address in Hønefoss.

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.