BIZTRAC BETA
Rental and operating of own or leased real estate

ETAT BOLIG AS

Org. no. 996067955 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 763,000
Operating profit NOK 148,000
Equity NOK 10.0m
Incorporated 2010
Share capital NOK 200,000

ETAT BOLIG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 996067955. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Drift og utvikling av fast eiendom. Selskapet skal også kunne delta i tilsvarende virksomhet gjennom aksjetegning.”. The most recent filed accounts, for the 2025 financial year, show NOK 763,000 in revenue and NOK 148,000 in operating profit.

Key figures · 2025

Revenue
NOK 763,000
Operating profit
NOK 148,000
Equity
NOK 10.0m
Est. value
NOK 7.1m

Financial health · 2025

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.8%
Good
Equity as a share of total capital

Who owns ETAT BOLIG AS?

GYLDENSKOG AS
ETAT BOLIG AS
NOK 763,000 rev. · NOK 148,000 profit

ETAT BOLIG AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ETAT BOLIG AS own?

ETAT BOLIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ETAT BOLIG AS

Who owns ETAT BOLIG AS?

GYLDENSKOG AS is the largest registered owner, with 50.0%.

What is the revenue of ETAT BOLIG AS?

ETAT BOLIG AS had revenue of NOK 763,000 in 2025.

Who is the general manager of ETAT BOLIG AS?

Tor Arne Brå is registered as general manager of ETAT BOLIG AS.

Where is ETAT BOLIG AS based?

ETAT BOLIG AS has its business address in Heimdal.

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.