biztrac. BETA
COMPANY REGISTER PROFILE
914632145 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KEEPON HOLDING AS

Org. no. 914632145 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 522,000
Incorporated 2014
Share capital NOK 261,000

Signals

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

KEEPON HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 914632145. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 261,000, divided into 45000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper, eie og drive fast eiendom samt gjøre næring av å kjøpe og selge valuta, ihendehaverobligasjoner og andre verdipapirer.”.

Key figures · 2025

Operating profit
NOK −18,000
▼ −18 %
Equity
NOK 522,000
▼ −3 %
Est. value
NOK 476,000

Financial health · 2025

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

Who owns KEEPON HOLDING AS?

KEEPON HOLDING AS
· NOK −18,000 profit

KEEPON HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KEEPON HOLDING AS own?

KEEPON HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KEEPON HOLDING AS

Who owns KEEPON HOLDING AS?

Torbjørn Moi is the largest registered owner, with 100.0%.

Who is the general manager of KEEPON HOLDING AS?

Torbjørn Moi is registered as general manager of KEEPON HOLDING AS.

Where is KEEPON HOLDING AS based?

KEEPON HOLDING AS has its business address in Indre Arna.

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.