BIZTRAC BETA
Uoppgitt

ERVIK PEDERSEN AS

Org. no. 921859236 Limited company (AS) Frøya Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −53,000
Equity NOK 18.0m
Incorporated 2018
Share capital NOK 958,000

Signals

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

ERVIK PEDERSEN AS is registered as a limited company in Frøya, Trøndelag with organisation number 921859236. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 958,000, divided into 2736324 shares. The company's stated purpose is: “Å eie aksjer i ett eller flere selskaper, og forvalte avkastningen.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −53,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −53,000
Equity
NOK 18.0m
Est. value
NOK 20.9m

Financial health · 2025

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

Who owns ERVIK PEDERSEN AS?

EIRIN ERVIK PEDERSEN
ERVIK PEDERSEN AS
NOK 0 rev. · NOK −53,000 profit

ERVIK PEDERSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERVIK PEDERSEN AS own?

ERVIK PEDERSEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ERVIK PEDERSEN AS

Who owns ERVIK PEDERSEN AS?

EIRIN ERVIK PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of ERVIK PEDERSEN AS?

ERVIK PEDERSEN AS had revenue of NOK 0 in 2025.

Who is the general manager of ERVIK PEDERSEN AS?

Eirin Ervik Pedersen is registered as general manager of ERVIK PEDERSEN AS.

Where is ERVIK PEDERSEN AS based?

ERVIK PEDERSEN AS has its business address in Dyrvik.

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.