BIZTRAC BETA
COMPANY REGISTER PROFILE
969998378 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

NOROPP V/AUNØIEN AUD

Org. no. 969998378 Sole proprietorship (ENK) Oppdal Active
Ownership graph ↗
Revenue 2025 NOK 310,000
Operating profit NOK 132,000
Equity NOK −81,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−81k kr).

NOROPP V/AUNØIEN AUD is registered as a sole proprietorship in Oppdal, Trøndelag with organisation number 969998378. The business is classified under accounting and bookkeeping (NACE 69.202). The most recent filed accounts, for the 2025 financial year, show NOK 310,000 in revenue and NOK 132,000 in operating profit.

Key figures · 2025

Revenue
NOK 310,000
Operating profit
NOK 132,000
Equity
NOK −81,000
Est. value
NOK 601,000

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-521.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NOROPP V/AUNØIEN AUD?

No shareholders are registered for NOROPP V/AUNØIEN AUD in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NOROPP V/AUNØIEN AUD

What is the revenue of NOROPP V/AUNØIEN AUD?

NOROPP V/AUNØIEN AUD had revenue of NOK 310,000 in 2025.

Where is NOROPP V/AUNØIEN AUD based?

NOROPP V/AUNØIEN AUD has its business address in Oppdal.

Property

Business address Lyngvegen 11B, 7340 Oppdal
Cadastral unit 5021-286/59/0/0
Building Enebolig · 1 unit

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.