BIZTRAC BETA
Roofing activities

BLIKKENSLAGER HARAM AS

Org. no. 925251151 Limited company (AS) Vestby Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK −9,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

BLIKKENSLAGER HARAM AS is registered as a limited company in Vestby, Akershus with organisation number 925251151. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Blikkenslager, tømrer og vaktmestertjenester. Selskapet vil kunne investere i aksjer og andeler i andre selskap”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −9,000
Equity
NOK 1.1m
Est. value
NOK 997,000

Financial health · 2025

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

Who owns BLIKKENSLAGER HARAM AS?

TOR ERIK HARAM
BLIKKENSLAGER HARAM AS
NOK 1.5m rev. · NOK −9,000 profit

BLIKKENSLAGER HARAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKKENSLAGER HARAM AS

Who owns BLIKKENSLAGER HARAM AS?

TOR ERIK HARAM is the largest registered owner, with 100.0%.

What is the revenue of BLIKKENSLAGER HARAM AS?

BLIKKENSLAGER HARAM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of BLIKKENSLAGER HARAM AS?

Tor Erik Haram is registered as general manager of BLIKKENSLAGER HARAM AS.

Where is BLIKKENSLAGER HARAM AS based?

BLIKKENSLAGER HARAM AS has its business address in Vestby.

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.