BIZTRAC BETA
COMPANY REGISTER PROFILE
933909360 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Computer programming activities

EBBO DA

Org. no. 933909360 General partnership with shared liability (DA) Frosta Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Equity NOK 0
Incorporated 2024

EBBO DA is registered as a general partnership with shared liability in Frosta, Trøndelag with organisation number 933909360. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. The company's stated purpose is: “Utvikling og drift av diverse web baserte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue.

Key figures · 2025

Revenue
NOK 0
Equity
NOK 0

Financial health · 2025

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

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

Who owns EBBO DA?

No shareholders are registered for EBBO DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about EBBO DA

What is the revenue of EBBO DA?

EBBO DA had revenue of NOK 0 in 2025.

Who is the general manager of EBBO DA?

Emre Sanden is registered as general manager of EBBO DA.

Where is EBBO DA based?

EBBO DA has its business address in Frosta.

Property

Business address Kjelsåsen 77, 7633 Frosta
Cadastral unit 5036-81/33/0/0
Building Enebolig · 2 units

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.