BIZTRAC BETA
Rental and operating of own or leased real estate

STUB EIENDOM AS

Org. no. 932163462 Limited company (AS) Sandefjord Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 556,000
Operating profit NOK 107,000
Equity NOK 42.7m
Incorporated 1982
Share capital NOK 10.2m

STUB EIENDOM AS is registered as a limited company in Sandefjord, Vestfold with organisation number 932163462. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 10.2m, divided into 3000 shares. The company's stated purpose is: “Å drive handel, drift av faste eiendommer, her- under kjøp, salg, oppføring og utleie, deltagelse i andre selskaper samt utføre konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 556,000 in revenue and NOK 107,000 in operating profit.

Key figures · 2024

Revenue
NOK 556,000
Operating profit
NOK 107,000
Equity
NOK 42.7m
Est. value
NOK 29.4m

Financial health · 2024

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

Who owns STUB EIENDOM AS?

SPEED INVEST AS
STUB EIENDOM AS
NOK 556,000 rev. · NOK 107,000 profit

STUB EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STUB EIENDOM AS own?

STUB EIENDOM AS holds stakes in 7 companies:

See the full ownership structure →

Group structure

STUB EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about STUB EIENDOM AS

Who owns STUB EIENDOM AS?

SPEED INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STUB EIENDOM AS?

STUB EIENDOM AS had revenue of NOK 556,000 in 2024.

Where is STUB EIENDOM AS based?

STUB EIENDOM AS has its business address in Sandefjord.

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.