BIZTRAC BETA
Rental and operating of own or leased real estate

A E TUFTE AS

Org. no. 816919312 Limited company (AS) Hol Incorporated 1935 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 6.2m
Incorporated 1935
Share capital NOK 180,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).

A E TUFTE AS is registered as a limited company in Hol, Buskerud with organisation number 816919312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1935. Registered share capital is NOK 180,000, divided into 180 shares. The company's stated purpose is: “Eie og leie ut forretningslokaler og leiligheter, samt egen forretningsdrift.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 6.2m
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns A E TUFTE AS?

PER ARNE TUFTE
A E TUFTE AS
NOK 0 rev. · NOK −24,000 profit

A E TUFTE AS has 4 registered shareholders:

All shareholders and roles →

Which companies does A E TUFTE AS own?

A E TUFTE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about A E TUFTE AS

Who owns A E TUFTE AS?

PER ARNE TUFTE is the largest registered owner, with 25.0%.

What is the revenue of A E TUFTE AS?

A E TUFTE AS had revenue of NOK 0 in 2024.

Who is the general manager of A E TUFTE AS?

Vigdis Inga Tufte Uthus is registered as general manager of A E TUFTE AS.

Where is A E TUFTE AS based?

A E TUFTE AS has its business address in Geilo.

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.