BIZTRAC BETA
Computer consultancy and computer facilities management activities

PEEKY AS

Org. no. 911817152 Limited company (AS) Sogndal Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 61,000
Operating profit NOK 30,000
Equity NOK −1.2m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,2 mill kr).

PEEKY AS is registered as a limited company in Sogndal, Vestland with organisation number 911817152. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikla og drifta nettbaserte tenester. Selskapet skal også kunna utføra konsulenttenester og fungera som eit holding- og investeringsselskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 61,000 in revenue and NOK 30,000 in operating profit.

Key figures · 2024

Revenue
NOK 61,000
Operating profit
NOK 30,000
Equity
NOK −1.2m
Est. value
NOK 121,000

Financial health · 2024

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-521.6%
Weak
Equity as a share of total capital

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

Who owns PEEKY AS?

GISLE LE NES
PEEKY AS
NOK 61,000 rev. · NOK 30,000 profit

PEEKY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PEEKY AS

Who owns PEEKY AS?

GISLE LE NES is the largest registered owner, with 100.0%.

What is the revenue of PEEKY AS?

PEEKY AS had revenue of NOK 61,000 in 2024.

Who is the general manager of PEEKY AS?

Gisle Le Nes is registered as general manager of PEEKY AS.

Where is PEEKY AS based?

PEEKY AS has its business address in Leikanger.

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.