BIZTRAC BETA
Other education activities

BJERKAAS AS

Org. no. 922898618 Limited company (AS) Lier Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 82,000
Operating profit NOK −27,000
Equity NOK 99,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

BJERKAAS AS is registered as a limited company in Lier, Buskerud with organisation number 922898618. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Yte konsulent- og opplæringstjenester knyttet til språkopplæring, risiko- og sårbarhetsanalyser samt beredskaps- og øvelsesplanlegging. Selskapet skal også påta seg trefellings- og håndverkeroppdrag.”. The most recent filed accounts, for the 2024 financial year, show NOK 82,000 in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 82,000
Operating profit
NOK −27,000
Equity
NOK 99,000
Est. value
NOK 116,000

Financial health · 2024

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

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

Who owns BJERKAAS AS?

ERIK BJERKAAS
BJERKAAS AS
NOK 82,000 rev. · NOK −27,000 profit

BJERKAAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJERKAAS AS

Who owns BJERKAAS AS?

ERIK BJERKAAS is the largest registered owner, with 100.0%.

What is the revenue of BJERKAAS AS?

BJERKAAS AS had revenue of NOK 82,000 in 2024.

Who is the general manager of BJERKAAS AS?

Erik Bjerkaas is registered as general manager of BJERKAAS AS.

Where is BJERKAAS AS based?

BJERKAAS AS has its business address in Lier.

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.