BIZTRAC BETA
Computer programming activities

ZOOPIT AS

Org. no. 816928672 Limited company (AS) Bærum Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK −2.0m
Equity NOK 529,000
Incorporated 2016
Employees 7
Share capital NOK 407,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,0 mill kr).
  • Nylig endring 2026-05-21 Adresseendring registrert 2026-05-21.

ZOOPIT AS is registered as a limited company in Bærum, Akershus with organisation number 816928672. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 407,000, divided into 406509 shares. The company's stated purpose is: “Utvikle, selge og drifte softwareløsninger for bestilling, optimering, gjennomføring av tjenester ved transport av varer, samt relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK −2.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK −2.0m
Equity
NOK 529,000
Est. value
NOK 8.7m

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.2%
Good
Equity as a share of total capital

Who owns ZOOPIT AS?

FUNIS AS
ZOOPIT AS
NOK 5.0m rev. · NOK −2.0m profit

ZOOPIT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZOOPIT AS

Who owns ZOOPIT AS?

FUNIS AS is the largest registered owner, with 92.0%.

What is the revenue of ZOOPIT AS?

ZOOPIT AS had revenue of NOK 5.0m in 2024.

Who is the general manager of ZOOPIT AS?

Nora Skabo Rieber-Mohn is registered as general manager of ZOOPIT AS.

Where is ZOOPIT AS based?

ZOOPIT AS has its business address in Fornebu.

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.