biztrac. BETA
COMPANY REGISTER PROFILE
929552997 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Civil engineering activities

GULSETH OG LIBRANDSEN AS

Org. no. 929552997 Limited company (AS) Rælingen Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −129
Equity NOK 22,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−129 kr).

GULSETH OG LIBRANDSEN AS is registered as a limited company in Rælingen, Akershus with organisation number 929552997. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 16 shares. The company's stated purpose is: “Eie andre selskaper.”.

Key figures · 2025

Operating profit
NOK −129
▲ +86 %
Equity
NOK 22,000
▼ −1 %
Est. value
NOK 36,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
42.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GULSETH OG LIBRANDSEN AS?

GULSETH OG LIBRANDSEN AS
· NOK −129 profit

GULSETH OG LIBRANDSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULSETH OG LIBRANDSEN AS own?

GULSETH OG LIBRANDSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULSETH OG LIBRANDSEN AS

Who owns GULSETH OG LIBRANDSEN AS?

Aleksander Liseth Gulbrandsen is the largest registered owner, with 100.0%.

Who is the general manager of GULSETH OG LIBRANDSEN AS?

Aleksander Liseth Gulbrandsen is registered as general manager of GULSETH OG LIBRANDSEN AS.

Where is GULSETH OG LIBRANDSEN AS based?

GULSETH OG LIBRANDSEN AS has its business address in Rælingen.

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.