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

ØSTRE ROSTEN 115 AS

Org. no. 918292047 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 3.3m
Equity NOK 18.7m
Incorporated 2016
Share capital NOK 112,000

ØSTRE ROSTEN 115 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 918292047. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 112,000, divided into 112 shares. The company's stated purpose is: “Å eie næringstomt, å oppføre næringsbygg og leie ut dette selv, eller ved å samarbeide med andre virksomheter å forestå investeringsvirksomhet, utvikling og salg av fast eiendom og annen virksomhet beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 3.3m in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
▲ +5 %
Operating profit
NOK 3.3m
▲ +6 %
Equity
NOK 18.7m
▲ +65 %
Est. value
NOK 19.6m

Financial health · 2025

Liquidity
12.48
Very good
Current assets ÷ current liabilities
Profitability
13.3%
Good
Return on total assets
Solidity
51.3%
Very good
Equity as a share of total capital

Who owns ØSTRE ROSTEN 115 AS?

ØSTRE ROSTEN 115 AS
NOK 4.3m rev. · NOK 3.3m profit

ØSTRE ROSTEN 115 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØSTRE ROSTEN 115 AS

Who owns ØSTRE ROSTEN 115 AS?

OTTO INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of ØSTRE ROSTEN 115 AS?

ØSTRE ROSTEN 115 AS had revenue of NOK 4.3m in 2025.

Where is ØSTRE ROSTEN 115 AS based?

ØSTRE ROSTEN 115 AS has its business address in Tiller.

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.