biztrac. BETA
COMPANY REGISTER PROFILE
915977715 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

MAASEIDE PROMOTION AS

Org. no. 915977715 Limited company (AS) Sandnes Incorporated 2015 Active
Operating profit NOK −1.2m
Equity NOK 210.6m
Incorporated 2015
Share capital NOK 1.1m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,2 mill kr).

MAASEIDE PROMOTION AS is registered as a limited company in Sandnes, Rogaland with organisation number 915977715. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 1.1m, divided into 30000 shares. The company's stated purpose is: “Bidra til verdiutvikling i hel- og deleide porteføljeselskaper, investeringsvirksomhet i selskaper, selskapsandeler og fast eiendom. Gjennom datterselskaper skal selskapet utvikle seg gjennom investeringer i helsesektoren, fast eiendom, sports-/fritidsmarkedet, event-virksomhet og hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −1.2m
▼ −41 %
Equity
NOK 210.6m
▼ −2 %
Est. value
NOK 268.7m

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
17.2%
Very good
Return on total assets
Solidity
68.5%
Very good
Equity as a share of total capital

Who owns MAASEIDE PROMOTION AS?

MAASEIDE PROMOTION AS
· NOK −1.2m profit

MAASEIDE PROMOTION AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MAASEIDE PROMOTION AS own?

MAASEIDE PROMOTION AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about MAASEIDE PROMOTION AS

Who owns MAASEIDE PROMOTION AS?

BFBK HOLDING AS is the largest registered owner, with 100.0%.

Where is MAASEIDE PROMOTION AS based?

MAASEIDE PROMOTION AS has its business address in Sandnes.

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.