biztrac. BETA
COMPANY REGISTER PROFILE
921887124 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other education activities

PPV LÆRESENTER AS

Org. no. 921887124 Limited company (AS) Bykle Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −35,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−35k kr).

PPV LÆRESENTER AS is registered as a limited company in Bykle, Agder with organisation number 921887124. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Opplæring i Guds visdom gjennom salg av bøker og nettkurs.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −35,000
▼ −0 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns PPV LÆRESENTER AS?

PPV LÆRESENTER AS
NOK 0 rev. · NOK 0 profit

PPV LÆRESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PPV LÆRESENTER AS

Who owns PPV LÆRESENTER AS?

Astrid Larsen is the largest registered owner, with 100.0%.

What is the revenue of PPV LÆRESENTER AS?

PPV LÆRESENTER AS had revenue of NOK 0 in 2025.

Who is the general manager of PPV LÆRESENTER AS?

Astrid Larsen is registered as general manager of PPV LÆRESENTER AS.

Where is PPV LÆRESENTER AS based?

PPV LÆRESENTER AS has its business address in Hovden I Setesdal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.