biztrac. BETA
COMPANY REGISTER PROFILE
984304943 ORG. NO. 2017 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other activities of other membership organisations

UNG I TRAFIKKEN - INGEN VENNER Å MISTE

Org. no. 984304943 Association/club/organisation (FLI) Oslo Incorporated 1976 Active
Ownership graph ↗
Revenue 2017 NOK 3.6m
Operating profit NOK 93,000
Equity NOK 260,000
Incorporated 1976
Employees 7

UNG I TRAFIKKEN - INGEN VENNER Å MISTE is registered as a association/club/organisation in Oslo, Oslo with organisation number 984304943. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1976 and has 7 registered employees. The most recent filed accounts, for the 2017 financial year, show NOK 3.6m in revenue and NOK 93,000 in operating profit.

Former names: MOTORFØRERNES AVHOLDSFORBUND UNGDOM

Key figures · 2017

Revenue
NOK 3.6m
Operating profit
NOK 93,000
Equity
NOK 260,000
Est. value
NOK 485,000

Financial health · 2017

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns UNG I TRAFIKKEN - INGEN VENNER Å MISTE?

No shareholders are registered for UNG I TRAFIKKEN - INGEN VENNER Å MISTE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about UNG I TRAFIKKEN - INGEN VENNER Å MISTE

What is the revenue of UNG I TRAFIKKEN - INGEN VENNER Å MISTE?

UNG I TRAFIKKEN - INGEN VENNER Å MISTE had revenue of NOK 3.6m in 2017.

Who is the general manager of UNG I TRAFIKKEN - INGEN VENNER Å MISTE?

Stig Eid Sandstad is registered as general manager of UNG I TRAFIKKEN - INGEN VENNER Å MISTE.

Where is UNG I TRAFIKKEN - INGEN VENNER Å MISTE based?

UNG I TRAFIKKEN - INGEN VENNER Å MISTE has its business address in Oslo.

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.