BIZTRAC BETA
Architectural activities

BORG ARKITEKTUR AS

Org. no. 913405862 Limited company (AS) Halden Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 644,000
Equity NOK 817,000
Incorporated 2014
Share capital NOK 30,000

BORG ARKITEKTUR AS is registered as a limited company in Halden, Østfold with organisation number 913405862. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Arkitekt og ingeniørtjenester, eiendomsutvikling og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 644,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 644,000
Equity
NOK 817,000
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns BORG ARKITEKTUR AS?

KARL PREPSL
BORG ARKITEKTUR AS
NOK 2.2m rev. · NOK 644,000 profit

BORG ARKITEKTUR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORG ARKITEKTUR AS

Who owns BORG ARKITEKTUR AS?

KARL PREPSL is the largest registered owner, with 100.0%.

What is the revenue of BORG ARKITEKTUR AS?

BORG ARKITEKTUR AS had revenue of NOK 2.2m in 2025.

Who is the general manager of BORG ARKITEKTUR AS?

Karl Prepsl is registered as general manager of BORG ARKITEKTUR AS.

Where is BORG ARKITEKTUR AS based?

BORG ARKITEKTUR AS has its business address in Tistedal.

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.