BIZTRAC BETA
Rental and operating of own or leased real estate

TØNSBERG BUTIKKEIENDOM EIK AS

Org. no. 975792196 Limited company (AS) Ringerike Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK 4.0m
Equity NOK 8.0m
Incorporated 1995
Share capital NOK 3.0m

Signals

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

TØNSBERG BUTIKKEIENDOM EIK AS is registered as a limited company in Ringerike, Buskerud with organisation number 975792196. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 3.0m, divided into 800 shares. The company's stated purpose is: “Å eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK 4.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK 4.0m
Equity
NOK 8.0m
Est. value
NOK 12.1m

Financial health · 2024

Liquidity
2.71
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.0%
Good
Equity as a share of total capital

Who owns TØNSBERG BUTIKKEIENDOM EIK AS?

AKA AS
TØNSBERG BUTIKKEIENDOM EIK AS
NOK 5.1m rev. · NOK 4.0m profit

TØNSBERG BUTIKKEIENDOM EIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØNSBERG BUTIKKEIENDOM EIK AS

Who owns TØNSBERG BUTIKKEIENDOM EIK AS?

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

What is the revenue of TØNSBERG BUTIKKEIENDOM EIK AS?

TØNSBERG BUTIKKEIENDOM EIK AS had revenue of NOK 5.1m in 2024.

Where is TØNSBERG BUTIKKEIENDOM EIK AS based?

TØNSBERG BUTIKKEIENDOM EIK AS has its business address in Hønefoss.

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.