BIZTRAC BETA
Other health services

LOGOPED ROLF H BORGE AS

Org. no. 976494970 Limited company (AS) Røst Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −19,000
Equity NOK 371,000
Incorporated 1996
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

LOGOPED ROLF H BORGE AS is registered as a limited company in Røst, Nordland with organisation number 976494970. The business is classified under other health services (NACE 86.993). The company was incorporated in 1996. Registered share capital is NOK 200,000, divided into 400 shares. The company's stated purpose is: “Logopedisk virksomhet samt salg av konfeksjonsvarer og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −19,000
Equity
NOK 371,000
Est. value
NOK 1.2m

Financial health · 2024

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.9%
Good
Equity as a share of total capital

Who owns LOGOPED ROLF H BORGE AS?

ROLF HARALD BORGE
LOGOPED ROLF H BORGE AS
NOK 1.2m rev. · NOK −19,000 profit

LOGOPED ROLF H BORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LOGOPED ROLF H BORGE AS

Who owns LOGOPED ROLF H BORGE AS?

ROLF HARALD BORGE is the largest registered owner, with 100.0%.

What is the revenue of LOGOPED ROLF H BORGE AS?

LOGOPED ROLF H BORGE AS had revenue of NOK 1.2m in 2024.

Who is the general manager of LOGOPED ROLF H BORGE AS?

Rolf Harald Borge is registered as general manager of LOGOPED ROLF H BORGE AS.

Where is LOGOPED ROLF H BORGE AS based?

LOGOPED ROLF H BORGE AS has its business address in Røst.

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.