BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

AI ACCOUNTING AS

Org. no. 917312516 Limited company (AS) Frogn Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −99,000
Equity NOK 168,000
Incorporated 2016
Share capital NOK 540,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−99k kr).

AI ACCOUNTING AS is registered as a limited company in Frogn, Akershus with organisation number 917312516. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2016. Registered share capital is NOK 540,000, divided into 30000 shares. The company's stated purpose is: “Å påta seg utredningsarbeid, konsulenttjenester samt økonomiske og tekniske rådgivningstjenester. Drift av støttefunksjoner og annen virksomhet som naturlig hører til dette. Selskapet skal også kunne investere i aksjer og verdipapirer, drifte, erverve og forvalte faste eiendommer samt å yte lån eller garantier for lån.”.

Key figures · 2025

Operating profit
NOK −99,000
Equity
NOK 168,000
Est. value
NOK 242,000

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.5%
Very good
Equity as a share of total capital

Who owns AI ACCOUNTING AS?

LARS PETTER WESSEL
AI ACCOUNTING AS
· NOK −99,000 profit

AI ACCOUNTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AI ACCOUNTING AS

Who owns AI ACCOUNTING AS?

LARS PETTER WESSEL is the largest registered owner, with 80.0%.

Who is the general manager of AI ACCOUNTING AS?

Lars Petter Wessel is registered as general manager of AI ACCOUNTING AS.

Where is AI ACCOUNTING AS based?

AI ACCOUNTING AS has its business address in Drøbak.

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.