BIZTRAC BETA
Buying and selling of own real estate

SHN TOMT 11 AS

Org. no. 920877400 Limited company (AS) Malvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −45,000
Equity NOK −4.8m
Incorporated 2018
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,8 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−45k kr).

SHN TOMT 11 AS is registered as a limited company in Malvik, Trøndelag with organisation number 920877400. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, herunder drive utvikling av eiendom samt virksomhet beslektet med dette, og deltakelse i andre selskaper med virksomhet som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −45,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −45,000
Equity
NOK −4.8m

Financial health · 2025

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

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

Who owns SHN TOMT 11 AS?

VULU EIENDOM AS
SHN TOMT 11 AS
NOK 0 rev. · NOK −45,000 profit

SHN TOMT 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SHN TOMT 11 AS

Who owns SHN TOMT 11 AS?

VULU EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SHN TOMT 11 AS?

SHN TOMT 11 AS had revenue of NOK 0 in 2025.

Where is SHN TOMT 11 AS based?

SHN TOMT 11 AS has its business address in Hommelvik.

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.