BIZTRAC BETA
Roofing activities

EIKER TAK OG BLIKK AS

Org. no. 914083028 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 44.0m
Operating profit NOK −1.4m
Equity NOK −1.9m
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,4 mill kr).

EIKER TAK OG BLIKK AS is registered as a limited company in Drammen, Buskerud with organisation number 914083028. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Taktekking og blikkenslagerarbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 44.0m in revenue and NOK −1.4m in operating profit.

Key figures · 2024

Revenue
NOK 44.0m
Operating profit
NOK −1.4m
Equity
NOK −1.9m

Financial health · 2024

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-23.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EIKER TAK OG BLIKK AS?

Tommy Smith
EIKER TAK OG BLIKK AS
NOK 44.0m rev. · NOK −1.4m profit

EIKER TAK OG BLIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKER TAK OG BLIKK AS

Who owns EIKER TAK OG BLIKK AS?

Tommy Smith is the largest registered owner, with 100.0%.

What is the revenue of EIKER TAK OG BLIKK AS?

EIKER TAK OG BLIKK AS had revenue of NOK 44.0m in 2024.

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

Tommy Smith is registered as general manager of EIKER TAK OG BLIKK AS.

Where is EIKER TAK OG BLIKK AS based?

EIKER TAK OG BLIKK AS has its business address in Solbergelva.

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.