BIZTRAC BETA
COMPANY REGISTER PROFILE
917006989 ORG. NO. 2022 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other activities of other membership organisations

FESTNINGSVEIEN VEL

Org. no. 917006989 Association/club/organisation (FLI) Sarpsborg Incorporated 2009 Active
Ownership graph ↗
Revenue 2022 NOK 15,000
Operating profit NOK 12,000
Equity NOK 162,000
Incorporated 2009

FESTNINGSVEIEN VEL is registered as a association/club/organisation in Sarpsborg, Østfold with organisation number 917006989. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2009. The most recent filed accounts, for the 2022 financial year, show NOK 15,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2022

Revenue
NOK 15,000
Operating profit
NOK 12,000
Equity
NOK 162,000
Est. value
NOK 126,000

Financial health · 2022

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

Who owns FESTNINGSVEIEN VEL?

No shareholders are registered for FESTNINGSVEIEN VEL in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FESTNINGSVEIEN VEL

What is the revenue of FESTNINGSVEIEN VEL?

FESTNINGSVEIEN VEL had revenue of NOK 15,000 in 2022.

Where is FESTNINGSVEIEN VEL based?

FESTNINGSVEIEN VEL has its business address in Greåker.

Property

Business address c/o Hans Beck-Hansen Festningsveien 15, 1719 Greåker
Cadastral unit 3105-2073/540/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.