BIZTRAC BETA
Construction of residential and non-residential buildings

OK BAD AS

Org. no. 992779926 Limited company (AS) Time Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 17.6m
Operating profit NOK 931,000
Equity NOK 548,000
Incorporated 2008
Employees 11
Share capital NOK 30,000

OK BAD AS is registered as a limited company in Time, Rogaland with organisation number 992779926. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2008 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Flislegging, rehabilitering/oppføring av bad, montering av kjøkken, tømmerarbeid, muring, og tjenester som naturlig hører sammen med dette. Takseringsarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.6m in revenue and NOK 931,000 in operating profit.

Key figures · 2025

Revenue
NOK 17.6m
Operating profit
NOK 931,000
Equity
NOK 548,000
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns OK BAD AS?

KÅRE LYE
OK BAD AS
NOK 17.6m rev. · NOK 931,000 profit

OK BAD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does OK BAD AS own?

OK BAD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OK BAD AS

Who owns OK BAD AS?

KÅRE LYE is the largest registered owner, with 50.0%.

What is the revenue of OK BAD AS?

OK BAD AS had revenue of NOK 17.6m in 2025.

Who is the general manager of OK BAD AS?

Oddmund Yri is registered as general manager of OK BAD AS.

Where is OK BAD AS based?

OK BAD AS has its business address in Lye.

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.