BIZTRAC BETA
COMPANY REGISTER PROFILE
935396786 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

AURVEGEN TOMT AS

Org. no. 935396786 Limited company (AS) Ullensaker Incorporated 2025 Active
Ownership graph ↗
Equity NOK 608,000
Incorporated 2025
Share capital NOK 52,000

Signals

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

AURVEGEN TOMT AS is registered as a limited company in Ullensaker, Akershus with organisation number 935396786. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 52,000, divided into 260000 shares. The company's stated purpose is: “Investere i og utvikle fast eiendom eller investere i selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2025

Equity
NOK 608,000
Est. value
NOK 331,000

Financial health · 2025

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

Who owns AURVEGEN TOMT AS?

AURVEGEN TOMT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AURVEGEN TOMT AS

Who owns AURVEGEN TOMT AS?

FRYDENLUND HOLDING AS is the largest registered owner, with 100.0%.

Where is AURVEGEN TOMT AS based?

AURVEGEN TOMT AS has its business address in Algarheim.

Property

Business address Ødegårdsalèen 27, 2056 Algarheim
Cadastral unit 3209-89/19/0/0
Building Våningshus · 1 unit

7 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.