BIZTRAC BETA
COMPANY REGISTER PROFILE
930011029 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Legal activities

ADVOKAT EIVIND NORDBY JOHNSEN

Org. no. 930011029 Sole proprietorship (ENK) Kristiansand Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.3m
Equity NOK 1.1m

ADVOKAT EIVIND NORDBY JOHNSEN is registered as a sole proprietorship in Kristiansand, Agder with organisation number 930011029. The business is classified under legal activities (NACE 69.100). The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.3m
Equity
NOK 1.1m
Est. value
NOK 5.1m

Financial health · 2025

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

Who owns ADVOKAT EIVIND NORDBY JOHNSEN?

No shareholders are registered for ADVOKAT EIVIND NORDBY JOHNSEN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ADVOKAT EIVIND NORDBY JOHNSEN

What is the revenue of ADVOKAT EIVIND NORDBY JOHNSEN?

ADVOKAT EIVIND NORDBY JOHNSEN had revenue of NOK 1.9m in 2025.

Where is ADVOKAT EIVIND NORDBY JOHNSEN based?

ADVOKAT EIVIND NORDBY JOHNSEN has its business address in Kristiansand S.

Property

Business address Tollbodgata 40, 4614 Kristiansand S
Cadastral unit 4204-150/1332/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

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