BIZTRAC BETA
COMPANY REGISTER PROFILE
979922035 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

BOGEN SERVICEBYGG AS

Org. no. 979922035 Limited company (AS) Evenes Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 441,000
Equity NOK 1.9m
Incorporated 1998
Share capital NOK 800,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOGEN SERVICEBYGG AS is registered as a limited company in Evenes, Nordland with organisation number 979922035. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 800,000, divided into 800 shares. The company's stated purpose is: “Kjøp og eller oppføring og bortleie av utleiebygg.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 441,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▲ +2 %
Operating profit
NOK 441,000
▲ +83 %
Equity
NOK 1.9m
▲ +4 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
3.12
Very good
Current assets ÷ current liabilities
Profitability
6.3%
Satisfactory
Return on total assets
Solidity
27.7%
Good
Equity as a share of total capital

Who owns BOGEN SERVICEBYGG AS?

BOGEN SERVICEBYGG AS
NOK 1.3m rev. · NOK 441,000 profit

BOGEN SERVICEBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOGEN SERVICEBYGG AS

Who owns BOGEN SERVICEBYGG AS?

SPAREBANK 68 GRADER NORD is the largest registered owner, with 100.0%.

What is the revenue of BOGEN SERVICEBYGG AS?

BOGEN SERVICEBYGG AS had revenue of NOK 1.3m in 2025.

Where is BOGEN SERVICEBYGG AS based?

BOGEN SERVICEBYGG AS has its business address in Bogen I Ofoten.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.