biztrac. BETA
COMPANY REGISTER PROFILE
913871324 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Holiday and other short-stay accommodation

ZEBRAFISH AS

Org. no. 913871324 Limited company (AS) Ullensaker Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 452,000
Operating profit NOK −805,000
Equity NOK 18.7m
Incorporated 2014
Share capital NOK 30,000

Signals

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

ZEBRAFISH AS is registered as a limited company in Ullensaker, Akershus with organisation number 913871324. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivning og investering i aksjer/eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 452,000 in revenue and NOK −805,000 in operating profit.

Key figures · 2025

Revenue
NOK 452,000
▼ −36 %
Operating profit
NOK −805,000
▼ −4358 %
Equity
NOK 18.7m
▼ −5 %
Est. value
NOK 24.7m

Financial health · 2025

Liquidity
5.23
Very good
Current assets ÷ current liabilities
Profitability
-3.6%
Not satisfactory
Return on total assets
Solidity
85.9%
Very good
Equity as a share of total capital

Who owns ZEBRAFISH AS?

ZEBRAFISH AS
NOK 452,000 rev. · NOK −805,000 profit

ZEBRAFISH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ZEBRAFISH AS own?

ZEBRAFISH AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ZEBRAFISH AS

Who owns ZEBRAFISH AS?

Øystein Arctander Rist is the largest registered owner, with 100.0%.

What is the revenue of ZEBRAFISH AS?

ZEBRAFISH AS had revenue of NOK 452,000 in 2025.

Where is ZEBRAFISH AS based?

ZEBRAFISH AS has its business address in Kløfta.

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

Report a problem

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