BIZTRAC BETA
COMPANY REGISTER PROFILE
970531823 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Legal activities

DIDRIK BRUN FERKINGSTAD

Org. no. 970531823 Sole proprietorship (ENK) Karmøy Active
Ownership graph ↗
Revenue 2024 NOK 987,000
Operating profit NOK 752,000
Equity NOK 3.8m

DIDRIK BRUN FERKINGSTAD is registered as a sole proprietorship in Karmøy, Rogaland with organisation number 970531823. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2024 financial year, show NOK 987,000 in revenue and NOK 752,000 in operating profit.

Former names: FERKINGSTAD DIDRIK, ADVOKAT DIDRIK FERKINGSTAD, ADVOKAT DIDRIK BRUN FERKINGSTAD

Key figures · 2024

Revenue
NOK 987,000
Operating profit
NOK 752,000
Equity
NOK 3.8m
Est. value
NOK 5.0m

Financial health · 2024

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

Who owns DIDRIK BRUN FERKINGSTAD?

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

Frequently asked questions about DIDRIK BRUN FERKINGSTAD

What is the revenue of DIDRIK BRUN FERKINGSTAD?

DIDRIK BRUN FERKINGSTAD had revenue of NOK 987,000 in 2024.

Where is DIDRIK BRUN FERKINGSTAD based?

DIDRIK BRUN FERKINGSTAD has its business address in Kopervik.

Property

Business address Kalvatræhagen 1, 4250 Kopervik
Cadastral unit 1149-64/347/0/0
Building Enebolig · 1 unit

5 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.