BIZTRAC BETA
COMPANY REGISTER PROFILE
920182410 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Manufacture of sports goods

PROFISHER AS

Org. no. 920182410 Limited company (AS) Vestby Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 21,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

PROFISHER AS is registered as a limited company in Vestby, Akershus with organisation number 920182410. The business is classified under manufacture of sports goods (NACE 32.300). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Produksjon og salg av fiskeutstyr og annet teknisk utstyr.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 21,000
Est. value
NOK 24,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns PROFISHER AS?

PROFISHER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROFISHER AS

Who owns PROFISHER AS?

KJELL YNGVE HOLE is the largest registered owner, with 34.0%.

Where is PROFISHER AS based?

PROFISHER AS has its business address in Son.

Property

Business address c/o Harald O. Osvold Skutebaugveien 32, 1555 Son
Cadastral unit 3216-133/43/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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