BIZTRAC BETA
Accounting and bookkeeping

LIKVID REGNSKAP AS

Org. no. 934094972 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 586,000
Operating profit NOK 13,000
Equity NOK 42,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

LIKVID REGNSKAP AS is registered as a limited company in Bærum, Akershus with organisation number 934094972. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av regnskapskontor.”. The most recent filed accounts, for the 2025 financial year, show NOK 586,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2025

Revenue
NOK 586,000
Operating profit
NOK 13,000
Equity
NOK 42,000
Est. value
NOK 83,000

Financial health · 2025

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LIKVID REGNSKAP AS?

TTHOLDING AS
LIKVID REGNSKAP AS
NOK 586,000 rev. · NOK 13,000 profit

LIKVID REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIKVID REGNSKAP AS

Who owns LIKVID REGNSKAP AS?

TTHOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIKVID REGNSKAP AS?

LIKVID REGNSKAP AS had revenue of NOK 586,000 in 2025.

Who is the general manager of LIKVID REGNSKAP AS?

Henriette Låker Hedemark is registered as general manager of LIKVID REGNSKAP AS.

Where is LIKVID REGNSKAP AS based?

LIKVID REGNSKAP AS has its business address in Skui.

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.