BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

TEG EIENDOM AS

Org. no. 812160192 Limited company (AS) Bærum Incorporated 1964 Active
Ownership graph ↗
Operating profit NOK −44,000
Equity NOK 3.5m
Incorporated 1964
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−44k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TEG EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 812160192. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1964. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og leie ut fast eiendom, investering i aksjer og andre verdipapirer og annet som står i denne forbindelse.”.

Key figures · 2024

Operating profit
NOK −44,000
Equity
NOK 3.5m
Est. value
NOK 4.4m

Financial health · 2024

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

Who owns TEG EIENDOM AS?

TRULS ESPEN GULBRANDSEN
TEG EIENDOM AS
· NOK −44,000 profit

TEG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEG EIENDOM AS own?

TEG EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TEG EIENDOM AS

Who owns TEG EIENDOM AS?

TRULS ESPEN GULBRANDSEN is the largest registered owner, with 100.0%.

Who is the general manager of TEG EIENDOM AS?

Truls Espen Gulbrandsen is registered as general manager of TEG EIENDOM AS.

Where is TEG EIENDOM AS based?

TEG EIENDOM AS has its business address in Eiksmarka.

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.