biztrac. BETA
COMPANY REGISTER PROFILE
985231400 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other personal service activities n.e.c.

EBBESTAD AS

Org. no. 985231400 Limited company (AS) Drammen Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 53,000
Operating profit NOK 43,000
Equity NOK 110,000
Incorporated 2002
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EBBESTAD AS is registered as a limited company in Drammen, Buskerud with organisation number 985231400. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av forbruksartikler, konsulenttjenester innen økonomi, samt porteføljeinvesteringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 53,000 in revenue and NOK 43,000 in operating profit.

Former names: TERRASSEN PAPARAZZI AS

Key figures · 2025

Revenue
NOK 53,000
▲ +92 %
Operating profit
NOK 43,000
▲ +184 %
Equity
NOK 110,000
▲ +10 %
Est. value
NOK 198,000

Financial health · 2025

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

Who owns EBBESTAD AS?

EBBESTAD AS
NOK 53,000 rev. · NOK 43,000 profit

EBBESTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EBBESTAD AS

Who owns EBBESTAD AS?

EBBESTAD REVISJON AS is the largest registered owner, with 100.0%.

What is the revenue of EBBESTAD AS?

EBBESTAD AS had revenue of NOK 53,000 in 2025.

Where is EBBESTAD AS based?

EBBESTAD AS has its business address in Svelvik.

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.