biztrac. BETA
COMPANY REGISTER PROFILE
826019352 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

ZENERGY SOLUTIONS AS

Org. no. 826019352 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −103,000
Equity NOK 401,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

ZENERGY SOLUTIONS AS is registered as a limited company in Bærum, Akershus with organisation number 826019352. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester, rådgivning innenfor energibransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −103,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −103,000
▼ −1604 %
Equity
NOK 401,000
▼ −29 %
Est. value
NOK 651,000

Financial health · 2025

Liquidity
21.13
Very good
Current assets ÷ current liabilities
Profitability
14.3%
Good
Return on total assets
Solidity
95.3%
Very good
Equity as a share of total capital

Who owns ZENERGY SOLUTIONS AS?

ZENERGY SOLUTIONS AS
NOK 0 rev. · NOK −103,000 profit

ZENERGY SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZENERGY SOLUTIONS AS

Who owns ZENERGY SOLUTIONS AS?

Sam Zarrabi is the largest registered owner, with 100.0%.

What is the revenue of ZENERGY SOLUTIONS AS?

ZENERGY SOLUTIONS AS had revenue of NOK 0 in 2025.

Who is the general manager of ZENERGY SOLUTIONS AS?

Sam Zarrabi is registered as general manager of ZENERGY SOLUTIONS AS.

Where is ZENERGY SOLUTIONS AS based?

ZENERGY SOLUTIONS AS has its business address in Stabekk.

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.