BIZTRAC BETA
Development of building projects

TEFT ENGAN AS

Org. no. 923039481 Limited company (AS) Nærøysund Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −77,000
Equity NOK 47,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

TEFT ENGAN AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 923039481. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling. Kjøp og salg av eiendom. Import og salg av byggevarer. Deltakelse i annen næringsvirksomhet og andre tjenester og produkter som naturlig faller sammen med dette, herunder delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer. Salg og utleie av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −77,000
Equity
NOK 47,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns TEFT ENGAN AS?

TEFT EIENDOMSUTVIKLING AS
TEFT ENGAN AS
· NOK −77,000 profit

TEFT ENGAN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TEFT ENGAN AS er morselskap for 18 datterselskaper:

Frequently asked questions about TEFT ENGAN AS

Who owns TEFT ENGAN AS?

TEFT EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

Where is TEFT ENGAN AS based?

TEFT ENGAN AS has its business address in Rørvik.

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.