BIZTRAC BETA
Marine fishing

CHRISTIANSEN KYSTFISKE AS

Org. no. 935265703 Limited company (AS) Vardø Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 548,000
Operating profit NOK −459,000
Equity NOK −548,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−548k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−459k kr).

CHRISTIANSEN KYSTFISKE AS is registered as a limited company in Vardø, Finnmark with organisation number 935265703. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive hav og kystfiske, samt eie fiskebåt til dette formålet.”. The most recent filed accounts, for the 2025 financial year, show NOK 548,000 in revenue and NOK −459,000 in operating profit.

Key figures · 2025

Revenue
NOK 548,000
Operating profit
NOK −459,000
Equity
NOK −548,000

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-27.9%
Weak
Equity as a share of total capital

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

Who owns CHRISTIANSEN KYSTFISKE AS?

PER ARNE CHRISTIANSEN
CHRISTIANSEN KYSTFISKE AS
NOK 548,000 rev. · NOK −459,000 profit

CHRISTIANSEN KYSTFISKE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHRISTIANSEN KYSTFISKE AS

Who owns CHRISTIANSEN KYSTFISKE AS?

PER ARNE CHRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of CHRISTIANSEN KYSTFISKE AS?

CHRISTIANSEN KYSTFISKE AS had revenue of NOK 548,000 in 2025.

Where is CHRISTIANSEN KYSTFISKE AS based?

CHRISTIANSEN KYSTFISKE AS has its business address in Vardø.

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.