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

NESBØ - DYRSTAD GRENDALAG

Org. no. 925226300 Association/club/organisation (FLI) Bremanger Incorporated 1985 Active
Ownership graph ↗
Revenue 2021 NOK 51,000
Operating profit NOK 31,000
Equity NOK 1.3m
Incorporated 1985

NESBØ - DYRSTAD GRENDALAG is registered as a association/club/organisation in Bremanger, Vestland with organisation number 925226300. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 1985. The most recent filed accounts, for the 2021 financial year, show NOK 51,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2021

Revenue
NOK 51,000
Operating profit
NOK 31,000
Equity
NOK 1.3m
Est. value
NOK 774,000

Financial health · 2021

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 NESBØ - DYRSTAD GRENDALAG?

No shareholders are registered for NESBØ - DYRSTAD GRENDALAG in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NESBØ - DYRSTAD GRENDALAG

What is the revenue of NESBØ - DYRSTAD GRENDALAG?

NESBØ - DYRSTAD GRENDALAG had revenue of NOK 51,000 in 2021.

Where is NESBØ - DYRSTAD GRENDALAG based?

NESBØ - DYRSTAD GRENDALAG has its business address in Svelgen.

Property

Business address Nesbøvegen 896, 6723 Svelgen
Cadastral unit 4648-35/15/0/0

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.