BIZTRAC BETA
Accounting and bookkeeping

Z REGNSKAP & RÅDGIVNING AS

Org. no. 933474437 Limited company (AS) Lørenskog Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 699,000
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

Z REGNSKAP & RÅDGIVNING AS is registered as a limited company in Lørenskog, Akershus with organisation number 933474437. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Regnskapstjenester og konsulenttjenester innen økonomisk og administrativ rådgivning for kunder. Selskapet skal også kunne investere i andre virksomheter med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 699,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 699,000
Equity
NOK 30,000
Est. value
NOK 2.2m

Financial health · 2025

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

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

Who owns Z REGNSKAP & RÅDGIVNING AS?

SIFFER INVEST AS
Z REGNSKAP & RÅDGIVNING AS
NOK 2.0m rev. · NOK 699,000 profit

Z REGNSKAP & RÅDGIVNING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Z REGNSKAP & RÅDGIVNING AS

Who owns Z REGNSKAP & RÅDGIVNING AS?

SIFFER INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of Z REGNSKAP & RÅDGIVNING AS?

Z REGNSKAP & RÅDGIVNING AS had revenue of NOK 2.0m in 2025.

Where is Z REGNSKAP & RÅDGIVNING AS based?

Z REGNSKAP & RÅDGIVNING AS has its business address in Fjellhamar.

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.