biztrac. BETA
COMPANY REGISTER PROFILE
914626390 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other health services

LOGOPED HOLE AS

Org. no. 914626390 Limited company (AS) Stavanger Incorporated 2014 Active
Revenue 2025 NOK 13,000
Operating profit NOK −80,000
Equity NOK 7.0m
Incorporated 2014
Share capital NOK 30,000

Signals

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

LOGOPED HOLE AS is registered as a limited company in Stavanger, Rogaland with organisation number 914626390. The business is classified under other health services (NACE 86.993). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å drive virksomhet innenfor logoped tjenester, samt investere overskuddslikviditet i ulike verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −80,000 in operating profit.

Key figures · 2025

Revenue
NOK 13,000
▼ −12 %
Operating profit
NOK −80,000
▲ +13 %
Equity
NOK 7.0m
▲ +8 %
Est. value
NOK 6.8m

Financial health · 2025

Liquidity
8.67
Very good
Current assets ÷ current liabilities
Profitability
7.1%
Satisfactory
Return on total assets
Solidity
88.5%
Very good
Equity as a share of total capital

Who owns LOGOPED HOLE AS?

LOGOPED HOLE AS
NOK 13,000 rev. · NOK −80,000 profit

LOGOPED HOLE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOGOPED HOLE AS

Who owns LOGOPED HOLE AS?

Kari Ingunn Hole is the largest registered owner, with 100.0%.

What is the revenue of LOGOPED HOLE AS?

LOGOPED HOLE AS had revenue of NOK 13,000 in 2025.

Who is the general manager of LOGOPED HOLE AS?

Kari Ingunn Hole is registered as general manager of LOGOPED HOLE AS.

Where is LOGOPED HOLE AS based?

LOGOPED HOLE AS has its business address in Stavanger.

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.