BIZTRAC BETA
Uoppgitt

GRADATIM FEROCITER AS

Org. no. 927385341 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 537,000
Equity NOK 1.6m
Incorporated 2021
Share capital NOK 30,000

GRADATIM FEROCITER AS is registered as a limited company in Bærum, Akershus with organisation number 927385341. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 537,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 537,000
Equity
NOK 1.6m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns GRADATIM FEROCITER AS?

BENDIK EIDE ANSKAU
GRADATIM FEROCITER AS
NOK 1.8m rev. · NOK 537,000 profit

GRADATIM FEROCITER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRADATIM FEROCITER AS

Who owns GRADATIM FEROCITER AS?

BENDIK EIDE ANSKAU is the largest registered owner, with 100.0%.

What is the revenue of GRADATIM FEROCITER AS?

GRADATIM FEROCITER AS had revenue of NOK 1.8m in 2024.

Who is the general manager of GRADATIM FEROCITER AS?

Bendik Eide Anskau is registered as general manager of GRADATIM FEROCITER AS.

Where is GRADATIM FEROCITER AS based?

GRADATIM FEROCITER AS has its business address in Lommedalen.

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.