BIZTRAC BETA
Roofing activities

BAKKES BLIKKENSLAGERVERKSTED AS

Org. no. 975989704 Limited company (AS) Stange Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 121,000
Operating profit NOK 38,000
Equity NOK 1.0m
Incorporated 1995
Share capital NOK 100,000

BAKKES BLIKKENSLAGERVERKSTED AS is registered as a limited company in Stange, Innlandet with organisation number 975989704. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Blikkenslagerverksted samt annen økonomisk virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 121,000 in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 121,000
Operating profit
NOK 38,000
Equity
NOK 1.0m
Est. value
NOK 569,000

Financial health · 2025

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

Who owns BAKKES BLIKKENSLAGERVERKSTED AS?

TROND BAKKE
BAKKES BLIKKENSLAGERVERKSTED AS
NOK 121,000 rev. · NOK 38,000 profit

BAKKES BLIKKENSLAGERVERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BAKKES BLIKKENSLAGERVERKSTED AS

Who owns BAKKES BLIKKENSLAGERVERKSTED AS?

TROND BAKKE is the largest registered owner, with 100.0%.

What is the revenue of BAKKES BLIKKENSLAGERVERKSTED AS?

BAKKES BLIKKENSLAGERVERKSTED AS had revenue of NOK 121,000 in 2025.

Who is the general manager of BAKKES BLIKKENSLAGERVERKSTED AS?

Trond Bakke is registered as general manager of BAKKES BLIKKENSLAGERVERKSTED AS.

Where is BAKKES BLIKKENSLAGERVERKSTED AS based?

BAKKES BLIKKENSLAGERVERKSTED AS has its business address in Ottestad.

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.