BIZTRAC BETA
COMPANY REGISTER PROFILE
916922736 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

PETER AS

Org. no. 916922736 Limited company (AS) Larvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −3,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

PETER AS is registered as a limited company in Larvik, Vestfold with organisation number 916922736. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å eie og forvalte aksjer og andre selskapsandeler, samt virksomhet som står i forbindelse med dette, herunder investering i både noterte og unoterte selskaper i Norge og utlandet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: EIE CONSULTING AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −3,000

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 PETER AS?

PETER AS
NOK 0 rev. · NOK 0 profit

PETER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PETER AS

Who owns PETER AS?

PETER HOLMENE RAUGLAND is the largest registered owner, with 100.0%.

What is the revenue of PETER AS?

PETER AS had revenue of NOK 0 in 2025.

Who is the general manager of PETER AS?

Peter Holmene Raugland is registered as general manager of PETER AS.

Where is PETER AS based?

PETER AS has its business address in Stavern.

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

Report a problem

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