BIZTRAC BETA
Traditional, complementary and alternative medicine activities

BRAGD INVEST AS

Org. no. 923342494 Limited company (AS) Lillehammer Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 390,000
Operating profit NOK 93,000
Equity NOK −15,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−15k kr).

BRAGD INVEST AS is registered as a limited company in Lillehammer, Innlandet with organisation number 923342494. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utførelse av kiropraktisk behandling og fysioterapi. Virksomheten vil også omfatte kjøp/salg/eie av aksjer i andre selskap samt investering i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 390,000 in revenue and NOK 93,000 in operating profit.

Key figures · 2025

Revenue
NOK 390,000
Operating profit
NOK 93,000
Equity
NOK −15,000
Est. value
NOK 526,000

Financial health · 2025

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-16.0%
Weak
Equity as a share of total capital

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

Who owns BRAGD INVEST AS?

KJETIL HENNINGSEN
BRAGD INVEST AS
NOK 390,000 rev. · NOK 93,000 profit

BRAGD INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRAGD INVEST AS

Who owns BRAGD INVEST AS?

KJETIL HENNINGSEN is the largest registered owner, with 50.0%.

What is the revenue of BRAGD INVEST AS?

BRAGD INVEST AS had revenue of NOK 390,000 in 2025.

Where is BRAGD INVEST AS based?

BRAGD INVEST AS has its business address in Fåberg.

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.