BIZTRAC BETA
Roofing activities

ODDA KOBBER OG BLIKK AS

Org. no. 997109643 Limited company (AS) Ullensvang Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −2,000
Equity NOK 252,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

ODDA KOBBER OG BLIKK AS is registered as a limited company in Ullensvang, Vestland with organisation number 997109643. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kobber og blikkenslagerarbeid, ventilasjon, isolering og kapsling og industrivedlikehold.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −2,000
Equity
NOK 252,000
Est. value
NOK 358,000

Financial health · 2024

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

Who owns ODDA KOBBER OG BLIKK AS?

SIGMUND REKKEDAL
ODDA KOBBER OG BLIKK AS
NOK 1.1m rev. · NOK −2,000 profit

ODDA KOBBER OG BLIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODDA KOBBER OG BLIKK AS

Who owns ODDA KOBBER OG BLIKK AS?

SIGMUND REKKEDAL is the largest registered owner, with 100.0%.

What is the revenue of ODDA KOBBER OG BLIKK AS?

ODDA KOBBER OG BLIKK AS had revenue of NOK 1.1m in 2024.

Who is the general manager of ODDA KOBBER OG BLIKK AS?

Sigmund Rekkedal is registered as general manager of ODDA KOBBER OG BLIKK AS.

Where is ODDA KOBBER OG BLIKK AS based?

ODDA KOBBER OG BLIKK AS has its business address in Odda.

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.