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

THOMASDALEN 1 AS

Org. no. 924567392 Limited company (AS) Gjøvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 892,000
Equity NOK 3.8m
Incorporated 2020
Share capital NOK 60,000

Signals

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

THOMASDALEN 1 AS is registered as a limited company in Gjøvik, Innlandet with organisation number 924567392. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg, samt utleie av eiendom. Selskapet kan eie andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 892,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
▼ −3 %
Operating profit
NOK 892,000
▲ +8 %
Equity
NOK 3.8m
▲ +2 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
5.98
Very good
Current assets ÷ current liabilities
Profitability
6.6%
Satisfactory
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns THOMASDALEN 1 AS?

THOMASDALEN 1 AS
NOK 2.0m rev. · NOK 892,000 profit

THOMASDALEN 1 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about THOMASDALEN 1 AS

Who owns THOMASDALEN 1 AS?

MURMESTER ALF V. OLSEN AS is the largest registered owner, with 89.0%.

What is the revenue of THOMASDALEN 1 AS?

THOMASDALEN 1 AS had revenue of NOK 2.0m in 2025.

Where is THOMASDALEN 1 AS based?

THOMASDALEN 1 AS has its business address in Gjøvik.

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.