BIZTRAC BETA
Other technical consultancy

EBIRKE INNOVATIONS AS

Org. no. 824861072 Limited company (AS) Lindesnes Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 169,000
Operating profit NOK 91,000
Equity NOK 706,000
Incorporated 2020
Share capital NOK 200,000

EBIRKE INNOVATIONS AS is registered as a limited company in Lindesnes, Agder with organisation number 824861072. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet, med hovedtyngde på mekanisk-, prosess- eller pharmasautisk industri og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 169,000 in revenue and NOK 91,000 in operating profit.

Key figures · 2024

Revenue
NOK 169,000
Operating profit
NOK 91,000
Equity
NOK 706,000
Est. value
NOK 769,000

Financial health · 2024

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

Who owns EBIRKE INNOVATIONS AS?

EBIRKE UTVIKLING AS
EBIRKE INNOVATIONS AS
NOK 169,000 rev. · NOK 91,000 profit

EBIRKE INNOVATIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EBIRKE INNOVATIONS AS

Who owns EBIRKE INNOVATIONS AS?

EBIRKE UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of EBIRKE INNOVATIONS AS?

EBIRKE INNOVATIONS AS had revenue of NOK 169,000 in 2024.

Where is EBIRKE INNOVATIONS AS based?

EBIRKE INNOVATIONS AS has its business address in Øyslebø.

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.