BIZTRAC BETA
COMPANY REGISTER PROFILE
995753596 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

FELLDAL CONSULTING AS

Org. no. 995753596 Limited company (AS) Bærum Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 520,000
Operating profit NOK 353,000
Equity NOK 656,000
Incorporated 2010
Share capital NOK 150,000

FELLDAL CONSULTING AS is registered as a limited company in Bærum, Akershus with organisation number 995753596. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2010. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Drive bedriftsrådgivning og investeringsvirksomhet, herunder å investere i fast eiendom og aksjer, samt det som ellers naturlig hører hertil.”. The most recent filed accounts, for the 2025 financial year, show NOK 520,000 in revenue and NOK 353,000 in operating profit.

Key figures · 2025

Revenue
NOK 520,000
Operating profit
NOK 353,000
Equity
NOK 656,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns FELLDAL CONSULTING AS?

NILS-JØRGEN NILSEN FELLDAL
FELLDAL CONSULTING AS
NOK 520,000 rev. · NOK 353,000 profit

FELLDAL CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FELLDAL CONSULTING AS

Who owns FELLDAL CONSULTING AS?

NILS-JØRGEN NILSEN FELLDAL is the largest registered owner, with 100.0%.

What is the revenue of FELLDAL CONSULTING AS?

FELLDAL CONSULTING AS had revenue of NOK 520,000 in 2025.

Where is FELLDAL CONSULTING AS based?

FELLDAL CONSULTING AS has its business address in Fornebu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.