BIZTRAC BETA
Other real estate activities on a fee or contract basis

OSLO BAD OG TAKST AS

Org. no. 933521141 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −12,000
Equity NOK 12,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

OSLO BAD OG TAKST AS is registered as a limited company in Oslo, Oslo with organisation number 933521141. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Virksomhet innen boligtaksering, eiendomsutvikling, konsultasjon innen eiendomsbransjen (inkludert interiørkonsultasjon) og byggeprosjektledelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −12,000
Equity
NOK 12,000
Est. value
NOK 13,000

Financial health · 2024

Liquidity
15.96
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
93.7%
Weak
Equity as a share of total capital

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

Who owns OSLO BAD OG TAKST AS?

NOH WEREDE
OSLO BAD OG TAKST AS
NOK 3,000 rev. · NOK −12,000 profit

OSLO BAD OG TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BAD OG TAKST AS

Who owns OSLO BAD OG TAKST AS?

NOH WEREDE is the largest registered owner, with 100.0%.

What is the revenue of OSLO BAD OG TAKST AS?

OSLO BAD OG TAKST AS had revenue of NOK 3,000 in 2024.

Where is OSLO BAD OG TAKST AS based?

OSLO BAD OG TAKST 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.