BIZTRAC BETA
COMPANY REGISTER PROFILE
825627502 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

STRAND-ERVIK HOLDING AS

Org. no. 825627502 Limited company (AS) Kinn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −93,000
Equity NOK 22.4m
Incorporated 2020
Share capital NOK 61,000

Signals

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

STRAND-ERVIK HOLDING AS is registered as a limited company in Kinn, Vestland with organisation number 825627502. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 61,000, divided into 122 shares. The company's stated purpose is: “Å være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −93,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −93,000
Equity
NOK 22.4m
Est. value
NOK 158.2m

Financial health · 2025

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

Who owns STRAND-ERVIK HOLDING AS?

STRAND-ERVIK HOLDING AS
NOK 0 rev. · NOK −93,000 profit

STRAND-ERVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRAND-ERVIK HOLDING AS

Who owns STRAND-ERVIK HOLDING AS?

RUNE ERVIK is the largest registered owner, with 100.0%.

What is the revenue of STRAND-ERVIK HOLDING AS?

STRAND-ERVIK HOLDING AS had revenue of NOK 0 in 2025.

Where is STRAND-ERVIK HOLDING AS based?

STRAND-ERVIK 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 25.08.2026.

Report a problem

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