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

GULOS AS

Org. no. 951370991 Limited company (AS) Skaun Incorporated 1989 Active
Revenue 2025 NOK 0
Operating profit NOK −252,000
Equity NOK 4.0m
Incorporated 1989
Share capital NOK 100,000

Signals

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

GULOS AS is registered as a limited company in Skaun, Trøndelag with organisation number 951370991. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Utvikle og drift av eiendom, samt utleie av maskinutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −252,000 in operating profit.

Former names: BØ-BO AS

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −252,000
▲ +13 %
Equity
NOK 4.0m
▼ −8 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
78.50
Very good
Current assets ÷ current liabilities
Profitability
9.0%
Satisfactory
Return on total assets
Solidity
98.9%
Very good
Equity as a share of total capital

Who owns GULOS AS?

GULOS AS
NOK 0 rev. · NOK −252,000 profit

GULOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULOS AS own?

GULOS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GULOS AS

Who owns GULOS AS?

Martin Kjøren is the largest registered owner, with 100.0%.

What is the revenue of GULOS AS?

GULOS AS had revenue of NOK 0 in 2025.

Who is the general manager of GULOS AS?

Martin Kjøren is registered as general manager of GULOS AS.

Where is GULOS AS based?

GULOS AS has its business address in Børsa.

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.