BIZTRAC BETA
COMPANY REGISTER PROFILE
934820355 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

Z INVEST AS

Org. no. 934820355 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 14,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

Z INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 934820355. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK 14,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns Z INVEST AS?

Z INVEST AS
· NOK −6,000 profit

Z INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Z INVEST AS

Who owns Z INVEST AS?

PIA ZCIMARZCECK is the largest registered owner, with 100.0%.

Who is the general manager of Z INVEST AS?

Pia Zcimarzceck is registered as general manager of Z INVEST AS.

Where is Z INVEST AS based?

Z INVEST AS has its business address in Bekkestua.

Property

Business address Kleivveien 34, 1356 Bekkestua
Cadastral unit 3201-18/58/0/0
Building Enebolig · 1 unit

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.