biztrac. BETA
COMPANY REGISTER PROFILE
914983762 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

STENSVIKEN 256 EIENDOM AS

Org. no. 914983762 Limited company (AS) Trondheim Incorporated 2014 Active
Revenue 2025 NOK 1.7m
Operating profit NOK 663,000
Equity NOK 6.8m
Incorporated 2014
Share capital NOK 1.1m

STENSVIKEN 256 EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914983762. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 1.1m, divided into 112948183 shares. The company's stated purpose is: “Å drive virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 663,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +5 %
Operating profit
NOK 663,000
▲ +7 %
Equity
NOK 6.8m
▼ −14 %
Est. value
NOK 6.3m

Financial health · 2025

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
10.8%
Good
Return on total assets
Solidity
53.8%
Very good
Equity as a share of total capital

Who owns STENSVIKEN 256 EIENDOM AS?

STENSVIKEN 256 EIENDOM AS
NOK 1.7m rev. · NOK 663,000 profit

STENSVIKEN 256 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENSVIKEN 256 EIENDOM AS

Who owns STENSVIKEN 256 EIENDOM AS?

SERE III NORWEGIAN RETAIL AS is the largest registered owner, with 100.0%.

What is the revenue of STENSVIKEN 256 EIENDOM AS?

STENSVIKEN 256 EIENDOM AS had revenue of NOK 1.7m in 2025.

Where is STENSVIKEN 256 EIENDOM AS based?

STENSVIKEN 256 EIENDOM 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.