biztrac. BETA
COMPANY REGISTER PROFILE
989869922 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

BORG OVERNATTING AS

Org. no. 989869922 Limited company (AS) Vestvågøy Incorporated 2006 Active
Revenue 2025 NOK 184,000
Operating profit NOK 60,000
Equity NOK 3.3m
Incorporated 2006
Share capital NOK 100,000

BORG OVERNATTING AS is registered as a limited company in Vestvågøy, Nordland with organisation number 989869922. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendom og finansielle instrumenter samt øvrige aktiviteter som naturlig kommer inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 184,000 in revenue and NOK 60,000 in operating profit.

Key figures · 2025

Revenue
NOK 184,000
▼ −63 %
Operating profit
NOK 60,000
▼ −85 %
Equity
NOK 3.3m
▲ +2 %
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
2.78
Very good
Current assets ÷ current liabilities
Profitability
1.9%
Weak
Return on total assets
Solidity
93.5%
Very good
Equity as a share of total capital

Who owns BORG OVERNATTING AS?

BORG OVERNATTING AS
NOK 184,000 rev. · NOK 60,000 profit

BORG OVERNATTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORG OVERNATTING AS

Who owns BORG OVERNATTING AS?

Inge Evald Elvebakk is the largest registered owner, with 100.0%.

What is the revenue of BORG OVERNATTING AS?

BORG OVERNATTING AS had revenue of NOK 184,000 in 2025.

Who is the general manager of BORG OVERNATTING AS?

Inge Evald Elvebakk is registered as general manager of BORG OVERNATTING AS.

Where is BORG OVERNATTING AS based?

BORG OVERNATTING AS has its business address in Bøstad.

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.