biztrac. BETA
COMPANY REGISTER PROFILE
934999037 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Preventive health care activities

FELBERG INVEST AS

Org. no. 934999037 Limited company (AS) Nordre Follo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).
  • Nylig endring 2026-08-31 Adresseendring registrert 2026-08-31.

FELBERG INVEST AS is registered as a limited company in Nordre Follo, Akershus with organisation number 934999037. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eie aksjer eller andeler i andre selskaper, samt investering og forvaltning av verdipapirer og annen kapitalforvaltning. Selskapet kan også delta i annen virksomhet som styret finner hensiktsmessig.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK 23,000
Est. value
NOK 36,000

Financial health · 2025

Liquidity
4.61
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
21.3%
Weak
Equity as a share of total capital

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

Who owns FELBERG INVEST AS?

FELBERG INVEST AS
· NOK −7,000 profit

FELBERG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FELBERG INVEST AS own?

FELBERG INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FELBERG INVEST AS

Who owns FELBERG INVEST AS?

Helge Andreas Felberg is the largest registered owner, with 100.0%.

Where is FELBERG INVEST AS based?

FELBERG INVEST AS has its business address in Oppegård.

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

Report a problem

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