BIZTRAC BETA
Buying and selling of own real estate

DATTEBAYO GRUPPEN AS

Org. no. 819761302 Limited company (AS) Skien Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −126,000
Equity NOK −69,000
Incorporated 2017
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−69k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−126k kr).

DATTEBAYO GRUPPEN AS is registered as a limited company in Skien, Telemark with organisation number 819761302. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handelsvirksomhet. Konsulenttjenester. Investering i aksjer og fond. Kjøp, salg og utleie av eiendom. Deltagelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −126,000
Equity
NOK −69,000

Financial health · 2024

Liquidity
3.87
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-35.4%
Weak
Equity as a share of total capital

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

Who owns DATTEBAYO GRUPPEN AS?

Lee Duc Trinh
DATTEBAYO GRUPPEN AS
· NOK −126,000 profit

DATTEBAYO GRUPPEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does DATTEBAYO GRUPPEN AS own?

DATTEBAYO GRUPPEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about DATTEBAYO GRUPPEN AS

Who owns DATTEBAYO GRUPPEN AS?

Lee Duc Trinh is the largest registered owner, with 51.0%.

Who is the general manager of DATTEBAYO GRUPPEN AS?

Lee Duc Trinh is registered as general manager of DATTEBAYO GRUPPEN AS.

Where is DATTEBAYO GRUPPEN AS based?

DATTEBAYO GRUPPEN AS has its business address in Skien.

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.