BIZTRAC BETA
COMPANY REGISTER PROFILE
965396713 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Business and other management consultancy activities

ELIN HELENE FJELLBERG

Org. no. 965396713 Sole proprietorship (ENK) Bærum Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.5m
Equity NOK 2,000

ELIN HELENE FJELLBERG is registered as a sole proprietorship in Bærum, Akershus with organisation number 965396713. The business is classified under business and other management consultancy activities (NACE 70.200). The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.5m
Equity
NOK 2,000
Est. value
NOK 4.8m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ELIN HELENE FJELLBERG?

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

Frequently asked questions about ELIN HELENE FJELLBERG

What is the revenue of ELIN HELENE FJELLBERG?

ELIN HELENE FJELLBERG had revenue of NOK 1.9m in 2025.

Where is ELIN HELENE FJELLBERG based?

ELIN HELENE FJELLBERG has its business address in Høvik.

Property

Business address Veritasveien 2, 1363 Høvik
Cadastral unit 3201-11/1140/0/0
Building Annen kontorbygning · 1 unit

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