BIZTRAC BETA
Other technical consultancy

ZERO EMISSION STUDIO AS

Org. no. 927954826 Limited company (AS) Nesodden Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 351,000
Equity NOK 1.0m
Incorporated 2021
Share capital NOK 30,000

ZERO EMISSION STUDIO AS is registered as a limited company in Nesodden, Akershus with organisation number 927954826. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen bærekraftrådgivning og arkitektur og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 351,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 351,000
Equity
NOK 1.0m
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.73
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
59.5%
Very good
Equity as a share of total capital

Who owns ZERO EMISSION STUDIO AS?

MICHAEL LOMMERTZ
ZERO EMISSION STUDIO AS
NOK 2.2m rev. · NOK 351,000 profit

ZERO EMISSION STUDIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ZERO EMISSION STUDIO AS

Who owns ZERO EMISSION STUDIO AS?

MICHAEL LOMMERTZ is the largest registered owner, with 100.0%.

What is the revenue of ZERO EMISSION STUDIO AS?

ZERO EMISSION STUDIO AS had revenue of NOK 2.2m in 2025.

Who is the general manager of ZERO EMISSION STUDIO AS?

Michael Lommertz is registered as general manager of ZERO EMISSION STUDIO AS.

Where is ZERO EMISSION STUDIO AS based?

ZERO EMISSION STUDIO AS has its business address in Nesodden.

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.