biztrac. BETA
COMPANY REGISTER PROFILE
929253671 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Roofing activities

BASTAVIK HOLDING AS

Org. no. 929253671 Limited company (AS) Kinn Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 2.2m
Equity NOK 7.7m
Incorporated 2022
Share capital NOK 30,000

BASTAVIK HOLDING AS is registered as a limited company in Kinn, Vestland with organisation number 929253671. 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 30000 shares. The company's stated purpose is: “Å eie og drive industrivirksomhet, basert på blikkenslager og isolasjon/ventilasjonsfag, samt utleie av eiendom og driftsmidler. Herunder å kunne gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 2.2m in operating profit.

Former names: NFH 220424 AS

Key figures · 2025

Revenue
NOK 3.4m
▲ +17 %
Operating profit
NOK 2.2m
▲ +10 %
Equity
NOK 7.7m
▲ +126 %
Est. value
NOK 9.5m

Financial health · 2025

Liquidity
4.50
Very good
Current assets ÷ current liabilities
Profitability
47.8%
Very good
Return on total assets
Solidity
38.8%
Good
Equity as a share of total capital

Who owns BASTAVIK HOLDING AS?

BASTAVIK HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BASTAVIK HOLDING AS own?

BASTAVIK HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about BASTAVIK HOLDING AS

Who owns BASTAVIK HOLDING AS?

SVOREN HOLDING AS is the largest registered owner, with 45.0%.

What is the revenue of BASTAVIK HOLDING AS?

BASTAVIK HOLDING AS had revenue of NOK 3.4m in 2025.

Where is BASTAVIK HOLDING AS based?

BASTAVIK HOLDING AS has its business address in Raudeberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.