BIZTRAC BETA
Roofing activities

BUSKERUD TAK OG BLIKK AS

Org. no. 827827142 Limited company (AS) Drammen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 12.8m
Operating profit NOK 1.2m
Equity NOK 956,000
Incorporated 2021
Share capital NOK 30,000

BUSKERUD TAK OG BLIKK AS is registered as a limited company in Drammen, Buskerud with organisation number 827827142. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Levering av tjenester og varer innen taktekker og blikkenslager. Herunder også vedlikeholdstjenester på fast eiendom og annet som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 12.8m
Operating profit
NOK 1.2m
Equity
NOK 956,000
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns BUSKERUD TAK OG BLIKK AS?

NILS JOHAN LARSEN
BUSKERUD TAK OG BLIKK AS
NOK 12.8m rev. · NOK 1.2m profit

BUSKERUD TAK OG BLIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUSKERUD TAK OG BLIKK AS

Who owns BUSKERUD TAK OG BLIKK AS?

NILS JOHAN LARSEN is the largest registered owner, with 100.0%.

What is the revenue of BUSKERUD TAK OG BLIKK AS?

BUSKERUD TAK OG BLIKK AS had revenue of NOK 12.8m in 2024.

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

Nils Johan Larsen is registered as general manager of BUSKERUD TAK OG BLIKK AS.

Where is BUSKERUD TAK OG BLIKK AS based?

BUSKERUD TAK OG BLIKK AS has its business address in Mjøndalen.

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.