BIZTRAC BETA
Rental and operating of own or leased real estate

ANDEBU SENTRUMSBYGG AS

Org. no. 951269956 Limited company (AS) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 1.3m
Equity NOK 2.6m
Incorporated 1989
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ANDEBU SENTRUMSBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 951269956. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Selskapets virksomhet er å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 1.3m
Equity
NOK 2.6m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns ANDEBU SENTRUMSBYGG AS?

SKRINDO HOLDING AS
ANDEBU SENTRUMSBYGG AS
NOK 3.3m rev. · NOK 1.3m profit

ANDEBU SENTRUMSBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANDEBU SENTRUMSBYGG AS

Who owns ANDEBU SENTRUMSBYGG AS?

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

What is the revenue of ANDEBU SENTRUMSBYGG AS?

ANDEBU SENTRUMSBYGG AS had revenue of NOK 3.3m in 2024.

Where is ANDEBU SENTRUMSBYGG AS based?

ANDEBU SENTRUMSBYGG AS has its business address in Oslo.

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.