BIZTRAC BETA
COMPANY REGISTER PROFILE
912844145 ORG. NO. 2017 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

ENGESLANDSTUNET SA

Org. no. 912844145 Co-operation (SA) Birkenes Incorporated 2013 Active
Ownership graph ↗
Equity NOK 0
Incorporated 2013

ENGESLANDSTUNET SA is registered as a co-operation in Birkenes, Agder with organisation number 912844145. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. The company's stated purpose is: “Bidra til at Engeslandstunet som består av hele eiendommen gnr 167 bnr 7 utvikles til å bli en møteplass for innbyggerne i Vegusdal. Foretaket skal selge tomter til bolig- og næringsformål fra gnr 167 bnr 7.”.

Key figures · 2017

Equity
NOK 0

Financial health · 2017

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 ENGESLANDSTUNET SA?

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

Frequently asked questions about ENGESLANDSTUNET SA

Who is the general manager of ENGESLANDSTUNET SA?

Trond Eirik Jaabæk is registered as general manager of ENGESLANDSTUNET SA.

Where is ENGESLANDSTUNET SA based?

ENGESLANDSTUNET SA has its business address in Engesland.

Property

Business address Engeslandsveien 1000, 4768 Engesland
Cadastral unit 4216-167/7/0/0
Building Helårsbolig benyttes som fritidsbolig · 1 unit

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.