BIZTRAC BETA
Development of building projects

SLETVOLDTUNET AS

Org. no. 991165649 Limited company (AS) Trondheim Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −239,000
Equity NOK −5.9m
Incorporated 2007
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5,9 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−239k kr).

SLETVOLDTUNET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 991165649. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −239,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −239,000
Equity
NOK −5.9m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1513846.7%
Weak
Equity as a share of total capital

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

Who owns SLETVOLDTUNET AS?

BOLIVA EIENDOM AS
SLETVOLDTUNET AS
NOK 0 rev. · NOK −239,000 profit

SLETVOLDTUNET AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLETVOLDTUNET AS

Who owns SLETVOLDTUNET AS?

BOLIVA EIENDOM AS is the largest registered owner, with 80.0%.

What is the revenue of SLETVOLDTUNET AS?

SLETVOLDTUNET AS had revenue of NOK 0 in 2025.

Who is the general manager of SLETVOLDTUNET AS?

Morten Lilleberg is registered as general manager of SLETVOLDTUNET AS.

Where is SLETVOLDTUNET AS based?

SLETVOLDTUNET AS has its business address in Trondheim.

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.