BIZTRAC BETA
Uoppgitt

FETTER ANTON INVEST AS

Org. no. 989127799 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −47,000
Equity NOK −1.7m
Incorporated 2005
Share capital NOK 170,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,7 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−47k kr).

FETTER ANTON INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 989127799. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 170,000, divided into 170000 shares. The company's stated purpose is: “Industriutvikling, konsulentvirksomhet og å forstå investeringsvirksomhet, eiendomsforvaltning og annen virksomhet beslektet med denne.”.

Key figures · 2025

Operating profit
NOK −47,000
Equity
NOK −1.7m

Financial health · 2025

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

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

Who owns FETTER ANTON INVEST AS?

IDA TERESE KOKKINN RIDENG
FETTER ANTON INVEST AS
· NOK −47,000 profit

FETTER ANTON INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FETTER ANTON INVEST AS own?

FETTER ANTON INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about FETTER ANTON INVEST AS

Who owns FETTER ANTON INVEST AS?

IDA TERESE KOKKINN RIDENG is the largest registered owner, with 100.0%.

Who is the general manager of FETTER ANTON INVEST AS?

Øyvind Rideng is registered as general manager of FETTER ANTON INVEST AS.

Where is FETTER ANTON INVEST AS based?

FETTER ANTON INVEST AS has its business address in Gjettum.

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.