BIZTRAC BETA
Development of building projects

MADLAMARK NÆRSERVICE AS

Org. no. 828259342 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −58,000
Equity NOK 107,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−58k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MADLAMARK NÆRSERVICE AS is registered as a limited company in Stavanger, Rogaland with organisation number 828259342. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utbygging, utvikling, oppføring, salg og utleie av eiendom, samt drift av fast eiendom og alt som står i forbindelse, herunder å delta i selskaper med samme formål.”.

Key figures · 2024

Operating profit
NOK −58,000
Equity
NOK 107,000
Est. value
NOK 98,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Not satisfactory
Equity as a share of total capital

Who owns MADLAMARK NÆRSERVICE AS?

MADLAMARK UTBYGGINGSSELSKAP AS
MADLAMARK NÆRSERVICE AS
· NOK −58,000 profit

MADLAMARK NÆRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MADLAMARK NÆRSERVICE AS

Who owns MADLAMARK NÆRSERVICE AS?

MADLAMARK UTBYGGINGSSELSKAP AS is the largest registered owner, with 100.0%.

Who is the general manager of MADLAMARK NÆRSERVICE AS?

Sigve Hebnes is registered as general manager of MADLAMARK NÆRSERVICE AS.

Where is MADLAMARK NÆRSERVICE AS based?

MADLAMARK NÆRSERVICE AS has its business address in Stavanger.

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.