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

TOMTEVEIEN 31 AS

Org. no. 994203444 Limited company (AS) Fredrikstad Incorporated 2009 Active
Revenue 2025 NOK 3.5m
Operating profit NOK 2.8m
Equity NOK 584,000
Incorporated 2009
Share capital NOK 100,000

Signals

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

TOMTEVEIEN 31 AS is registered as a limited company in Fredrikstad, Østfold with organisation number 994203444. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investering i-, drift, utleie, forvaltning og utvikling av, fast eiendom og alt som er naturlig forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
▲ +77 %
Operating profit
NOK 2.8m
▲ +81 %
Equity
NOK 584,000
▼ −3 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
4.00
Very good
Current assets ÷ current liabilities
Profitability
22.8%
Very good
Return on total assets
Solidity
4.3%
Weak
Equity as a share of total capital

Who owns TOMTEVEIEN 31 AS?

TOMTEVEIEN 31 AS
NOK 3.5m rev. · NOK 2.8m profit

TOMTEVEIEN 31 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOMTEVEIEN 31 AS

Who owns TOMTEVEIEN 31 AS?

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

What is the revenue of TOMTEVEIEN 31 AS?

TOMTEVEIEN 31 AS had revenue of NOK 3.5m in 2025.

Where is TOMTEVEIEN 31 AS based?

TOMTEVEIEN 31 AS has its business address in Fredrikstad.

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.