BIZTRAC BETA
Rental and operating of own or leased real estate

YMSE INVESTERINGER AS

Org. no. 820019792 Limited company (AS) Risør Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 245,000
Operating profit NOK 145,000
Equity NOK 15.7m
Incorporated 2017
Share capital NOK 50,000

YMSE INVESTERINGER AS is registered as a limited company in Risør, Agder with organisation number 820019792. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 6250 shares. The company's stated purpose is: “Handel med aksjer, andeler og verdipapirer i andre selskaper. Selskapet skal også kunne foreta investeringer i ulike finansielle instrumenter, investeringer i annen næringsaktivitet samt kjøp og salg samt utleie av eiendommer og alt som står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 245,000 in revenue and NOK 145,000 in operating profit.

Key figures · 2025

Revenue
NOK 245,000
Operating profit
NOK 145,000
Equity
NOK 15.7m
Est. value
NOK 11.1m

Financial health · 2024

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

Who owns YMSE INVESTERINGER AS?

ANNE CHRISTINE BANG
YMSE INVESTERINGER AS
NOK 245,000 rev. · NOK 145,000 profit

YMSE INVESTERINGER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about YMSE INVESTERINGER AS

Who owns YMSE INVESTERINGER AS?

ANNE CHRISTINE BANG is the largest registered owner, with 28.0%.

What is the revenue of YMSE INVESTERINGER AS?

YMSE INVESTERINGER AS had revenue of NOK 245,000 in 2025.

Where is YMSE INVESTERINGER AS based?

YMSE INVESTERINGER AS has its business address in Risør.

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.