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

SOMA EIENDOM AS

Org. no. 919298146 Limited company (AS) Nord-Fron Incorporated 2017 Active
Revenue 2025 NOK 709,000
Operating profit NOK 473,000
Equity NOK 785,000
Incorporated 2017
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SOMA EIENDOM AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 919298146. 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 200,000, divided into 200 shares. The company's stated purpose is: “Drift av fast eiendom og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 709,000 in revenue and NOK 473,000 in operating profit.

Key figures · 2025

Revenue
NOK 709,000
▲ +3 %
Operating profit
NOK 473,000
▲ +7 %
Equity
NOK 785,000
▲ +2 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
2.41
Very good
Current assets ÷ current liabilities
Profitability
10.9%
Good
Return on total assets
Solidity
17.6%
Satisfactory
Equity as a share of total capital

Who owns SOMA EIENDOM AS?

SOMA EIENDOM AS
NOK 709,000 rev. · NOK 473,000 profit

SOMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOMA EIENDOM AS

Who owns SOMA EIENDOM AS?

VA 365 EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SOMA EIENDOM AS?

SOMA EIENDOM AS had revenue of NOK 709,000 in 2025.

Where is SOMA EIENDOM AS based?

SOMA EIENDOM AS has its business address in Vinstra.

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.