BIZTRAC BETA
Uoppgitt

MATILDE FIBORG INVEST AS

Org. no. 931444212 Limited company (AS) Levanger Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 16,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

MATILDE FIBORG INVEST AS is registered as a limited company in Levanger, Trøndelag with organisation number 931444212. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen investering i aksjer og verdipapirer - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2024

Operating profit
NOK −7,000
Equity
NOK 16,000
Est. value
NOK 19,000

Financial health · 2024

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

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

Who owns MATILDE FIBORG INVEST AS?

MATILDE FIBORG
MATILDE FIBORG INVEST AS
· NOK −7,000 profit

MATILDE FIBORG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MATILDE FIBORG INVEST AS own?

MATILDE FIBORG INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MATILDE FIBORG INVEST AS

Who owns MATILDE FIBORG INVEST AS?

MATILDE FIBORG is the largest registered owner, with 100.0%.

Who is the general manager of MATILDE FIBORG INVEST AS?

Matilde Fiborg is registered as general manager of MATILDE FIBORG INVEST AS.

Where is MATILDE FIBORG INVEST AS based?

MATILDE FIBORG INVEST AS has its business address in Ekne.

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.