BIZTRAC BETA
Rental and operating of own or leased real estate

ST. OLAVS PLASS 1 SMN AS

Org. no. 999263380 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 3.0m
Equity NOK 51.6m
Incorporated 2012
Share capital NOK 1.0m

ST. OLAVS PLASS 1 SMN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999263380. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 1.0m, divided into 100000 shares. The company's stated purpose is: “Eie, drifte og utvikle eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 3.0m in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 3.0m
Equity
NOK 51.6m
Est. value
NOK 43.3m

Financial health · 2024

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

Who owns ST. OLAVS PLASS 1 SMN AS?

SPAREBANK 1 SMN
ST. OLAVS PLASS 1 SMN AS
NOK 7.5m rev. · NOK 3.0m profit

ST. OLAVS PLASS 1 SMN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ST. OLAVS PLASS 1 SMN AS er morselskap for 12 datterselskaper:

Frequently asked questions about ST. OLAVS PLASS 1 SMN AS

Who owns ST. OLAVS PLASS 1 SMN AS?

SPAREBANK 1 SMN is the largest registered owner, with 100.0%.

What is the revenue of ST. OLAVS PLASS 1 SMN AS?

ST. OLAVS PLASS 1 SMN AS had revenue of NOK 7.5m in 2024.

Who is the general manager of ST. OLAVS PLASS 1 SMN AS?

Aud Jardtrud Mulelid is registered as general manager of ST. OLAVS PLASS 1 SMN AS.

Where is ST. OLAVS PLASS 1 SMN AS based?

ST. OLAVS PLASS 1 SMN 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.