BIZTRAC BETA
COMPANY REGISTER PROFILE
997258428 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Other captive investment companies

LIBRICOLAE AS

Org. no. 997258428 Limited company (AS) Bærum Incorporated 2011 Active
Ownership graph ↗
Operating profit NOK −46,000
Equity NOK 60,000
Incorporated 2011
Share capital NOK 100,000

Signals

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

LIBRICOLAE AS is registered as a limited company in Bærum, Akershus with organisation number 997258428. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Som holdingselskap å investere i aksjer og andre deltaker- og eierinstrumenter og andre finansplasseringer, samt eie og utvikle fast eiendom, tilby konsulenttjenester innen interimledelse og ledelsesrådgiving, samt annen virksomhet som står i forbindelse med dette.”.

Former names: WM QUAESTOR AS

Key figures · 2024

Operating profit
NOK −46,000
Equity
NOK 60,000
Est. value
NOK 114,000

Financial health · 2024

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

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

Who owns LIBRICOLAE AS?

LIBRICOLAE HOLDING AS
LIBRICOLAE AS
· NOK −46,000 profit

LIBRICOLAE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIBRICOLAE AS

Who owns LIBRICOLAE AS?

LIBRICOLAE HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of LIBRICOLAE AS?

Kai Mjaanes is registered as general manager of LIBRICOLAE AS.

Where is LIBRICOLAE AS based?

LIBRICOLAE AS has its business address in Stabekk.

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.