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

GUNNAR BORGEN EIENDOM AS

Org. no. 980956016 Limited company (AS) Skien Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 489,000
Equity NOK 1.4m
Incorporated 1999
Share capital NOK 100,000

GUNNAR BORGEN EIENDOM AS is registered as a limited company in Skien, Telemark with organisation number 980956016. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 489,000 in operating profit.

Former names: GB EIENDOM AS

Key figures · 2025

Revenue
NOK 1.1m
▼ −2 %
Operating profit
NOK 489,000
▲ +4 %
Equity
NOK 1.4m
▲ +22 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
12.0%
Good
Return on total assets
Solidity
36.0%
Good
Equity as a share of total capital

Who owns GUNNAR BORGEN EIENDOM AS?

GUNNAR BORGEN EIENDOM AS
NOK 1.1m rev. · NOK 489,000 profit

GUNNAR BORGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GUNNAR BORGEN EIENDOM AS

Who owns GUNNAR BORGEN EIENDOM AS?

GUNNAR BORGEN is the largest registered owner, with 100.0%.

What is the revenue of GUNNAR BORGEN EIENDOM AS?

GUNNAR BORGEN EIENDOM AS had revenue of NOK 1.1m in 2025.

Who is the general manager of GUNNAR BORGEN EIENDOM AS?

Gunnar Borgen is registered as general manager of GUNNAR BORGEN EIENDOM AS.

Where is GUNNAR BORGEN EIENDOM AS based?

GUNNAR BORGEN EIENDOM AS has its business address in Skien.

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.