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

MARLI AS

Org. no. 923478558 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 145,000
Operating profit NOK 5,000
Equity NOK 2.3m
Incorporated 2019
Share capital NOK 60,000

Signals

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

MARLI AS is registered as a limited company in Bergen, Vestland with organisation number 923478558. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 145,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 145,000
▼ −97 %
Operating profit
NOK 5,000
▼ −100 %
Equity
NOK 2.3m
▲ +0 %
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.3%
Not satisfactory
Return on total assets
Solidity
210.6%
Very good
Equity as a share of total capital

Who owns MARLI AS?

MARLI AS
NOK 145,000 rev. · NOK 5,000 profit

MARLI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARLI AS

Who owns MARLI AS?

LUND EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of MARLI AS?

MARLI AS had revenue of NOK 145,000 in 2025.

Who is the general manager of MARLI AS?

Tom-Erik Seierslund is registered as general manager of MARLI AS.

Where is MARLI AS based?

MARLI AS has its business address in Sandsli.

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.