BIZTRAC BETA
Roofing activities

BLIKKENSLAGERMESTER KARL FLISRAM AS

Org. no. 929816838 Limited company (AS) Askøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 860,000
Operating profit NOK 43,000
Equity NOK 149,000
Incorporated 2022
Share capital NOK 30,000

BLIKKENSLAGERMESTER KARL FLISRAM AS is registered as a limited company in Askøy, Vestland with organisation number 929816838. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Blikkenslagerarbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 860,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 860,000
Operating profit
NOK 43,000
Equity
NOK 149,000
Est. value
NOK 196,000

Financial health · 2024

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

Who owns BLIKKENSLAGERMESTER KARL FLISRAM AS?

KARL FLISRAM
BLIKKENSLAGERMESTER KARL FLISRAM AS
NOK 860,000 rev. · NOK 43,000 profit

BLIKKENSLAGERMESTER KARL FLISRAM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKKENSLAGERMESTER KARL FLISRAM AS

Who owns BLIKKENSLAGERMESTER KARL FLISRAM AS?

KARL FLISRAM is the largest registered owner, with 100.0%.

What is the revenue of BLIKKENSLAGERMESTER KARL FLISRAM AS?

BLIKKENSLAGERMESTER KARL FLISRAM AS had revenue of NOK 860,000 in 2024.

Who is the general manager of BLIKKENSLAGERMESTER KARL FLISRAM AS?

Karl Flisram is registered as general manager of BLIKKENSLAGERMESTER KARL FLISRAM AS.

Where is BLIKKENSLAGERMESTER KARL FLISRAM AS based?

BLIKKENSLAGERMESTER KARL FLISRAM AS has its business address in Hauglandshella.

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.