BIZTRAC BETA
Roofing activities

BLEKKSLAGARN AS

Org. no. 926044486 Limited company (AS) Oppdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 77,000
Equity NOK 1.0m
Incorporated 2020
Share capital NOK 100,000

BLEKKSLAGARN AS is registered as a limited company in Oppdal, Trøndelag with organisation number 926044486. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å produsere og selge kobber - og blikkenslager produkter, samt kjøp og salg av andre produkter/tjenester som naturlig hører sammen med dette, 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 2024 financial year, show NOK 2.9m in revenue and NOK 77,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 77,000
Equity
NOK 1.0m
Est. value
NOK 773,000

Financial health · 2024

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

Who owns BLEKKSLAGARN AS?

JON SKANCKE ØIAMO
BLEKKSLAGARN AS
NOK 2.9m rev. · NOK 77,000 profit

BLEKKSLAGARN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BLEKKSLAGARN AS

Who owns BLEKKSLAGARN AS?

JON SKANCKE ØIAMO is the largest registered owner, with 50.0%.

What is the revenue of BLEKKSLAGARN AS?

BLEKKSLAGARN AS had revenue of NOK 2.9m in 2024.

Who is the general manager of BLEKKSLAGARN AS?

Jon Skancke Øiamo is registered as general manager of BLEKKSLAGARN AS.

Where is BLEKKSLAGARN AS based?

BLEKKSLAGARN AS has its business address in Oppdal.

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.