BIZTRAC BETA
Roofing activities

BLIKK OG SVEIS AS

Org. no. 998064430 Limited company (AS) Alta Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK −19,000
Equity NOK 764,000
Incorporated 2012
Employees 5
Share capital NOK 30,000

Signals

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

BLIKK OG SVEIS AS is registered as a limited company in Alta, Finnmark with organisation number 998064430. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Blikkenslager og sveising samt drive med annen økonomisk virksomhet som har naturlig sammenheng med dette, herunder deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK −19,000
Equity
NOK 764,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns BLIKK OG SVEIS AS?

JAN-INGE NILSEN
BLIKK OG SVEIS AS
NOK 3.2m rev. · NOK −19,000 profit

BLIKK OG SVEIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BLIKK OG SVEIS AS

Who owns BLIKK OG SVEIS AS?

JAN-INGE NILSEN is the largest registered owner, with 100.0%.

What is the revenue of BLIKK OG SVEIS AS?

BLIKK OG SVEIS AS had revenue of NOK 3.2m in 2025.

Who is the general manager of BLIKK OG SVEIS AS?

Guri-Marie Johansen is registered as general manager of BLIKK OG SVEIS AS.

Where is BLIKK OG SVEIS AS based?

BLIKK OG SVEIS AS has its business address in Alta.

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.