BIZTRAC BETA
Support activities for fishing and aquaculture

TRELLEVIK SERVICE 1 AS

Org. no. 933207404 Limited company (AS) Øygarden Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 1,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

TRELLEVIK SERVICE 1 AS is registered as a limited company in Øygarden, Vestland with organisation number 933207404. The business is classified under support activities for fishing and aquaculture (NACE 03.300). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Akvakulturtjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 1,000
Est. value
NOK 1,000

Financial health · 2025

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

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

Who owns TRELLEVIK SERVICE 1 AS?

ØYVIND TRELLEVIK
TRELLEVIK SERVICE 1 AS
NOK 0 rev. · NOK −16,000 profit

TRELLEVIK SERVICE 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRELLEVIK SERVICE 1 AS

Who owns TRELLEVIK SERVICE 1 AS?

ØYVIND TRELLEVIK is the largest registered owner, with 100.0%.

What is the revenue of TRELLEVIK SERVICE 1 AS?

TRELLEVIK SERVICE 1 AS had revenue of NOK 0 in 2025.

Who is the general manager of TRELLEVIK SERVICE 1 AS?

Øyvind Trellevik is registered as general manager of TRELLEVIK SERVICE 1 AS.

Where is TRELLEVIK SERVICE 1 AS based?

TRELLEVIK SERVICE 1 AS has its business address in Steinsland.

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.