BIZTRAC BETA
Repair and maintenance of civilian ships and boats

EBBESTAD PERFORMANCE AS

Org. no. 998620813 Limited company (AS) Asker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 22,000
Incorporated 2012
Share capital NOK 30,000

EBBESTAD PERFORMANCE AS is registered as a limited company in Asker, Akershus with organisation number 998620813. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive med reparasjon, salg, utleie og kjøp av biler og båter samt tilhørende produkter og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns EBBESTAD PERFORMANCE AS?

HANS-PETTER EBBESTAD
EBBESTAD PERFORMANCE AS
NOK 0 rev. · NOK 0 profit

EBBESTAD PERFORMANCE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EBBESTAD PERFORMANCE AS

Who owns EBBESTAD PERFORMANCE AS?

HANS-PETTER EBBESTAD is the largest registered owner, with 100.0%.

What is the revenue of EBBESTAD PERFORMANCE AS?

EBBESTAD PERFORMANCE AS had revenue of NOK 0 in 2025.

Who is the general manager of EBBESTAD PERFORMANCE AS?

Hans-Petter Ebbestad is registered as general manager of EBBESTAD PERFORMANCE AS.

Where is EBBESTAD PERFORMANCE AS based?

EBBESTAD PERFORMANCE AS has its business address in Heggedal.

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.